We are proud to share our inclusion in the 2024 Gartner Magic Quadrant for Data Integration Tools. We believe this recognition reflects the differentiated business outcomes CData delivers to our customers.
Get the Report →How to Use CData Connect to Access Live PingOne Data in Power Automate
CData Connect for PingOne enables you to integrate PingOne data into workflows built using Microsoft Power Automate Desktop.
CData Connect enables you to access live PingOne data in workflow automation tools like Power Automate. This article shows how to integrate PingOne data into a simple workflow, moving PingOne data into a CSV file.
CData Connect provides a pure SQL interface for PingOne, allowing you to easily integrate with live PingOne data in Power Automate — without replicating the data. Connect looks exactly like a SQL Server database to Power Automate and uses optimized data processing out of the box to push all supported SQL operations (filters, JOINs, etc) directly to PingOne, leveraging server-side processing to quickly return PingOne data.
Create a Virtual SQL Database for PingOne Data
CData Connect Server uses a straightforward, point-and-click interface to connect to data sources and generate APIs.
- Log into Connect Server and click Connections.
- Select "PingOne" from Available Data Sources.
-
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:
- From the home page of your PingOne organization, move to the navigation sidebar and click Environments.
- 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.
- In the environment's home page navigation sidebar, click Applications.
- Find your OAuth or Worker application details in the list.
-
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:
- The driver obtains an access token from PingOne and uses it to request data.
- 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.
- Click Save Changes
- Click Privileges -> Add and add the new user (or an existing user) with the appropriate permissions.
How to Integrate PingOne Data into Power Automate Workflows
After configuring CData Connect with PingOne, you are ready to integrate PingOne data into your Power Automate workflows. Open Microsoft Power Automate, add a new flow, and name the flow.

In the flow editor, you can add the actions to connect to PingOne, query PingOne using SQL, and write the query results to a CSV document.
Add an Open SQL Connection Action
Add an "Open SQL connection" action (Actions -> Database) and click the option to build the Connection string. In the Data Link Properties wizard:
- On the Provider tab: select Microsoft OLE DB Driver for SQL Server
- On the Connection tab:
- Select or enter a server name: set to the address and port of the SQL (TDS) endpoint of CData Connect, separated by a comma (e.g. localhost,8033)
- Enter information to log onto the server: select "Use a specific username and password" and use CData Connect credentials
- Select the database: use the database configured above (e.g. PingOne1)
- Click "Test Connection" to ensure the connection is configured properly
- Click "OK"
After building the connection string in the Data Link Properties wizard, save the action.

Add an Execute SQL Statement Action
Add an "Execute SQL statement" action (Actions -> Database) and configure the properties.
- Get connection by: SQL connection variable
- SQL connection: %SQLConnection% (the variable from the "Open SQL connection" action above)
- SQL statement: SELECT * FROM [CData].[Administrators].Users
After configuring the properties, save the action.

Add a Write to CSV File Action
Add a "Write to CSV file" action (Actions -> File) and configure the properties.
- Variable to write to: %QueryResult% (the variable from the "Execute SQL statement" action above)
- File path: set to a file on disk
- Configure Advanced settings as needed.
After configuring the properties, save the action.

Add a Close SQL Connection Action
Add a "Close SQL connection" action (Actions -> Database) and configure the properties.
- SQL Connection: %SQLConnection% (the variable from the "Open SQL connection" action above)
After configuring the properties, save the action.

Save & Run the Flow
Once you have configured all the actions for the flow, click the disk icon to save the flow. Click the play icon to run the flow.

Now you have a workflow to move PingOne data into a CSV file.

With CData Connect, you get live connectivity to PingOne data within your Microsoft Power Automate workflows.
Related Power Automate Articles
This article walks through using CData Connect Server with Power Automate Desktop. Check out our other articles for more ways to work with Power Automate (Desktop & Online):