Build Voice Agents in ElevenLabs with access to Live PingOne Data

ElevenLabs is a leading AI audio platform that enables developers to build conversational voice agents capable of natural, human-like interactions. The ElevenLabs Conversational AI platform allows you to create voice-powered assistants that can reason through tasks, respond dynamically, and interact with external systems in real time.

By integrating ElevenLabs with CData Connect AI through the MCP (Model Context Protocol), your voice agents gain the ability to query, analyze, and act on live PingOne data during conversations. This integration bridges ElevenLabs' conversational AI framework with the governed enterprise connectivity of CData Connect AI, ensuring all data access runs securely against authorized sources without manual data movement.

This article outlines the steps to configure PingOne connectivity in Connect AI, generate the required authentication credentials, register the Connect AI MCP Server in ElevenLabs, and verify that your voice agent can successfully interact with live PingOne data during conversations.

Step 1: Configure PingOne connectivity for ElevenLabs

Connectivity to PingOne from ElevenLabs is made possible through CData Connect AI's Remote MCP Server. To interact with PingOne data from your voice agents, 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 ElevenLabs. 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 (e.g., "ElevenLabs Voice Agent") 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, ElevenLabs can now connect to PingOne data through Connect AI.

Step 2: Add the Connect AI MCP Server in ElevenLabs

ElevenLabs supports connecting to external MCP servers that use SSE (Server-Sent Events) or HTTP streamable transport. The CData Connect AI Remote MCP Server is compatible with this integration.

1. Log into the ElevenLabs platform and navigate to your agent dashboard
2. Go to Integrations and click + Add Integration to access the MCP server integrations section
3. Click on Custom MCP Server to add a new integration
4. Enter the following configuration:
   • Name: CData Connect AI
   • Description: Access live enterprise data from hundreds of sources
   • Server URL: https://mcp.cloud.cdata.com/sse
   • Secret Token: Leave empty (authentication is handled via headers)
   • HTTP Headers: Add a header with key Authorization and value Basic your_email:your_PAT
   
5. Replace your_email:your_PAT with your Connect AI login email and the Personal Access Token you created earlier. For example: Basic [email protected]:ABC123...XYZ789
6. Click Save to test the connection and retrieve available tools from Connect AI
7. The CData Connect AI MCP server is now available to assign to your voice agents

Step 3: Configure your Voice Agent to use Connect AI

With the MCP server registered, you can now add it to your ElevenLabs voice agents to enable real-time data access during conversations.

1. Create a new agent or edit an existing agent in the ElevenLabs dashboard
2. In the agent configuration, navigate to the Tools section
3. Add the CData Connect AI MCP server you configured in Step 2
4. Configure the tool approval mode based on your requirements:
   • Always Ask: The agent will request permission before each data query (recommended for sensitive data)
   • Fine-Grained: Set approval requirements per tool/action
   • No Approval: The agent can query data autonomously
5. Save your agent configuration

Step 4: Interact with live data through your Voice Agent

Your ElevenLabs voice agent can now access and query live PingOne data through the CData Connect AI MCP Server during conversations.

1. Start a conversation with your voice agent
2. Ask your agent data-related questions such as:
   • "What connections are available?"
   • "Show me the schemas for PingOne"
   • "Query recent records from PingOne data"
   • "Summarize our latest Data"
3. The agent will use the Connect AI MCP tools to retrieve live data and respond conversationally

Your ElevenLabs voice agent is now fully configured to access and query live PingOne data through the CData Connect AI Remote MCP Server, enabling real-time, data-driven voice interactions for your users.

Get CData Connect AI

To access hundreds of SaaS, Big Data, and NoSQL sources through secure, AI-ready interfaces, try CData Connect AI today.