How to Access Live PingOne Data in Power Automate Desktop via ODBC

Jerod Johnson
Director, Technology Evangelism

The CData ODBC Driver for PingOne enables you to integrate PingOne data into workflows built using Microsoft Power Automate Desktop.

The CData ODBC Driver for PingOne 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.

Through optimized data processing, CData ODBC Drivers offer unmatched performance for interacting with live PingOne data in Microsoft Power Automate. When you issue complex SQL queries from Power Automate to PingOne, the driver pushes supported SQL operations, like filters and aggregations, directly to PingOne and utilizes the embedded SQL engine to process unsupported operations client-side (e.g. SQL functions and JOIN operations).

Connect to PingOne as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

To connect to PingOne, configure these properties:

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

Configuring 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 to the value of the Environment ID field.

Configuring 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 to OAuth.

Desktop Applications

Get and Refresh the OAuth Access Token

After setting the following, you are ready to connect:

: GETANDREFRESH. To avoid the need to repeat the OAuth exchange and manually setting the each time you connect, use .
: The Client ID you obtained when you created your custom OAuth application.
: The Client Secret you obtained when you created your custom OAuth application.
: 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 , 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.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing workflows.

Integrate PingOne Data into Power Automate Workflows

After configuring the DSN for 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.

👁 A new flow in Power Automate

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 configure the properties.

Connection string: DSN=CData PingOne Source

After configuring the action, click Save.

👁 A configured 'Open SQL connection' 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 action, click Save.

👁 A configured 'Execute SQL statement' 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 action, click Save.

👁 A configured 'Write to CSV file' 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 action, click Save.

👁 A configured 'Close SQL connection' 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.

👁 A fully configured workflow

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

👁 Application data in a CSV file (Salesforce is shown)

With the CData ODBC Driver for PingOne, you get live connectivity to PingOne data within your Microsoft Power Automate workflows.

URL: https://www.cdata.com/kb/tech/pingone-odbc-power-automate.rst