Integrating Gumloop with Cvent Data via CData Connect AI
Gumloop is a visual automation platform designed to create AI-powered workflows by combining triggers, AI nodes, APIs, and data connectors. By integrating Gumloop with CData Connect AI through the built-in MCP (Model Context Protocol) Server, workflows can seamlessly access and interact with live Cvent data.
The platform provides a low-code environment, making it easier to orchestrate complex processes without heavy development effort. Its flexibility allows integration across multiple business applications, enabling end-to-end automation with live data.
This article outlines the steps required to configure Cvent connectivity in Connect AI, register the MCP server in Gumloop, and build a workflow that queries Cvent data.
Step 1: Configure Cvent Connectivity for Gumloop
Connectivity to Cvent from Gumloop is made possible through CData Connect AI's Remote MCP Server. To interact with Cvent data from Gumloop, we start by creating and configuring a Cvent connection in CData Connect AI.
- Log into Connect AI, click Sources, and then click Add Connection
- Select "Cvent" from the Add Connection panel
-
Enter the necessary authentication properties to connect to Cvent.
Before you can authenticate to Cvent, you must create a workspace and an OAuth application.
Creating a Workspace
To create a workspace:
- Sign into Cvent and navigate to App Switcher (the blue button in the upper right corner of the page) >> Admin.
- In the Admin menu, navigate to Integrations >> REST API.
- A new tab launches for Developer Management. Click on Manage API Access in the new tab.
- Create a Workspace and name it. Select the scopes you would like your developers to have access to. Scopes control what data domains the developer can access.
- Choose All to allow developers to choose any scope, and any future scopes added to the REST API.
- Choose Custom to limit the scopes developers can choose for their OAuth apps to selected scopes. To access all tables exposed by the driver, you need to set the following scopes:
event/attendees:read event/attendees:write event/contacts:read event/contacts:write event/custom-fields:read event/custom-fields:write event/events:read event/events:write event/sessions:delete event/sessions:read event/sessions:write event/speakers:delete event/speakers:read event/speakers:write budget/budget-items:read budget/budget-items:write exhibitor/exhibitors:read exhibitor/exhibitors:write survey/surveys:read survey/surveys:write
Creating an OAuth Application
After you have set up a Workspace and invited them, developers can sign up and create a custom OAuth app. See the Creating a Custom OAuth Application section in the Help documentation for more information.
Connecting to Cvent
After creating an OAuth application, set the following connection properties to connect to Cvent:
- InitiateOAuth: GETANDREFRESH. Used to automatically get and refresh the OAuthAccessToken.
- OAuthClientId: The Client ID associated with the OAuth application. You can find this on the Applications page in the Cvent Developer Portal.
- OAuthClientSecret: The Client secret associated with the OAuth application. You can find this on the Applications page in the Cvent Developer Portal.
- Click Save & Test
-
Navigate to the Permissions tab in the Add Cvent Connection page and update the User-based permissions.
Add a Personal Access Token
A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Gumloop. It is best practice to create a separate PAT for each service to maintain granularity of access.
- Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
- On the Settings page, go to the Access Tokens section and click Create PAT.
-
Give the PAT a name and click Create.
- The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.
With the Cvent connection configured and a PAT generated, Gumloop is prepared to connect to Cvent data through the CData MCP server.
Step 2: Connect to the MCP server in Gumloop
The MCP server endpoint and authentication values from Connect AI must be added to Gumloop credentials.
- Sign in to Gumloop and create an account
- Visit the Gumloop Credentials page to configure MCP server
- Click on Add Credentials and search and select MCP Server
- Provide the following details:
- URL: https://mcp.cloud.cdata.com/mcp
- Label: A descriptive name such as Cvent-mcp-server
- Access Token / API Key: leave blank
- Additional Header: Authorization: Basic YOUR EMAIL:YOUR PAT
- Save the credentials
The MCP server is now available to build workflows in Gumloop.
Step 3: Build a workflow and explore live Cvent data with Gumloop
- Visit Gumloop Personal workspace and click on the Create Flow
- Select the icon or press Ctrl + B to add a node or a subflow
- Search for Ask AI and select it
- Click Show More Options and enable the Connect MCP Server? option
- From the MCP Servers dropdown, choose the saved MCP credential
- Add a Prompt and Choose an AI Model according to your requirements
- After configuring the required details, Click Run to run the pipeline
With the workflow run completed, Gumloop demonstrates successful retrieval of Cvent data through the CData Connect AI MCP server, with the MCP Client node providing the ability to ask questions, retrieve records, and perform actions on the data.
Get CData Connect AI
To get live data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today!