Build Agents in Relevance AI with Access to Live PingOne Data via CData Connect AI

Relevance AI is an AI automation and agent-building platform that enables organizations to create autonomous workflows powered by natural language reasoning. Users can visually design agents that interact with APIs, databases, and third-party systems to complete everyday business tasks or data operations.

By integrating Relevance AI with CData Connect AI through the built-in MCP (Model Context Protocol) Server, your agents can query, summarize, and act on live PingOne data in real time. This connection bridges Relevance AI intelligent workflow engine with the governed enterprise connectivity of CData Connect AI ensuring every query runs securely against authorized sources without manual data export.

This article outlines the steps to configure PingOne connectivity in Connect AI, register Connect AI in Relevance AI, and build an agent that interacts with live PingOne data.

Step 1: Configure PingOne Connectivity for Relevance AI

Connectivity to PingOne from Relevance AI is made possible through CData Connect AI's Remote MCP Server. To interact with PingOne data from Relevance AI, we start by creating and configuring a PingOne connection in CData Connect AI.

1. Log into Connect AI, click Sources, and then click Add Connection

2. Select PingOne from the Add Connection panel

3. Enter the necessary authentication properties to connect to PingOne.

   To connect to PingOne, configure these properties:

   • Region: The region where the data for your PingOne organization is being hosted.
   • AuthScheme: The type of authentication to use when connecting to PingOne.
   • Either WorkerAppEnvironmentId (required when using the default PingOne domain) or AuthorizationServerURL, configured as described below.

   Configuring WorkerAppEnvironmentId

   WorkerAppEnvironmentId is the ID of the PingOne environment in which your Worker application resides. This parameter is used only when the environment is using the default PingOne domain (auth.pingone). It is configured after you have created the custom OAuth application you will use to authenticate to PingOne, as described in Creating a Custom OAuth Application in the Help documentation.

   First, find the value for this property:

   1. From the home page of your PingOne organization, move to the navigation sidebar and click Environments.
   2. Find the environment in which you have created your custom OAuth/Worker application (usually Administrators), and click Manage Environment. The environment's home page displays.
   3. In the environment's home page navigation sidebar, click Applications.
   4. Find your OAuth or Worker application details in the list.
   5. Copy the value in the Environment ID field. It should look similar to:
      

      WorkerAppEnvironmentId='11e96fc7-aa4d-4a60-8196-9acf91424eca'

   Now set WorkerAppEnvironmentId to the value of the Environment ID field.

   Configuring AuthorizationServerURL

   AuthorizationServerURL is the base URL of the PingOne authorization server for the environment where your application is located. This property is only used when you have set up a custom domain for the environment, as described in the PingOne platform API documentation. See Custom Domains.

   Authenticating to PingOne with OAuth

   PingOne supports both OAuth and OAuthClient authentication. In addition to performing the configuration steps described above, there are two more steps to complete to support OAuth or OAuthCliet authentication:

   • Create and configure a custom OAuth application, as described in Creating a Custom OAuth Application in the Help documentation.
   • To ensure that the driver can access the entities in Data Model, confirm that you have configured the correct roles for the admin user/worker application you will be using, as described in Administrator Roles in the Help documentation.
   • Set the appropriate properties for the authscheme and authflow of your choice, as described in the following subsections.

   OAuth (Authorization Code grant)

   Set AuthScheme to OAuth.

   Desktop Applications

   Get and Refresh the OAuth Access Token

   After setting the following, you are ready to connect:

   • InitiateOAuth: GETANDREFRESH. To avoid the need to repeat the OAuth exchange and manually setting the OAuthAccessToken each time you connect, use InitiateOAuth.
   • OAuthClientId: The Client ID you obtained when you created your custom OAuth application.
   • OAuthClientSecret: The Client Secret you obtained when you created your custom OAuth application.
   • CallbackURL: The redirect URI you defined when you registered your custom OAuth application. For example: https://localhost:3333

   When you connect, the driver opens PingOne's OAuth endpoint in your default browser. Log in and grant permissions to the application. The driver then completes the OAuth process:

   1. The driver obtains an access token from PingOne and uses it to request data.
   2. The OAuth values are saved in the location specified in OAuthSettingsLocation, to be persisted across connections.

   The driver refreshes the access token automatically when it expires.

   For other OAuth methods, including Web Applications, Headless Machines, or Client Credentials Grant, refer to the Help documentation.

   
4. Click Save & Test
5. Navigate to the Permissions tab and update user-based permissions

Add a Personal Access Token

A Personal Access Token (PAT) is used to authenticate the connection to Connect AI from Relevance AI. It is best practice to create a separate PAT for each integration to maintain granular access control.

1. Click the gear icon () at the top right of the Connect AI app to open Settings
2. On the Settings page, go to the Access Tokens section and click Create PAT
3. Give the PAT a descriptive name and click Create

4. Copy the token when displayed and store it securely. It will not be shown again

With the PingOne connection configured and a PAT generated, Relevance AI can now connect to PingOne data through Connect AI.

Step 2: Configure Connectivity in Relevance AI

The CData Connect AI MCP endpoint and authorization details are registered within Relevance AI so that agents can call live data from Connect AI.

1. Sign in to Relevance AI and create an account if you do not already have one
2. From the sidebar, navigate to Agents and then click on New Agent

3. Select Build from scratch and name the agent (eg; CData MCP Server)

4. Inside the agent editor, select Advanced and then switch to the MCP Server tab

5. Click + Add Remote MCP Tools
6. In the dialog that appears, fill out the fields as follows:
• URL: https://mcp.cloud.cdata.com/mcp
• Label: Any custom label (eg; cdata_mcp_server)
• Authentication: Select Custom headers
• Add header key:value pair. Combine your email and PAT as email:PAT and encode that string in Base64 and then prefix with the word Basic
  • Key: Authorization
  • Value: Basic base64(email:PAT)

Click Connect to establish the connection. Relevance AI will verify your credentials and register the CData Connect AI MCP Server for use in agents.

Step 3: Build and Run a Relevance AI Agent with Live PingOne Data

1. Switch to the Run tab for your agent
2. Enter a task for example, "List the five most recent incidents from ServiceNow"

3. The agent will query Connect AI via the MCP endpoint and display live results from PingOne data

With the connection complete, Relevance AI agents can now issue queries, retrieve records, and perform AI-driven tasks over live PingOne data through CData Connect AI MCP Server.

Get CData Connect AI

To access hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, try CData Connect AI today!