Integrate PingOne Data into Automated Tasks with Power Automate

Power Automate (Microsoft Flow) is an online service that automates events (known as workflows) across the most common apps and services. When paired with CData Connect Server, you get instant, cloud-to-cloud access to PingOne data for visualizations, dashboards, and more. This article shows how to connect to Connect Server from Power Automate and integrate live PingOne data into your workflows and tasks.

CData Connect Server provides a pure SQL interface for PingOne, allowing you to easily integrate with live PingOne data in Power Automate — without replicating the data. CData Connect Server 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.

1. Login to Connect Server and click Connections.
2. Select "PingOne" from Available Data Sources.
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 Changes
5. Click Privileges -> Add and add the new user (or an existing user) with the appropriate permissions.

Connecting to CData Connect Server

To use Connect Server to integrate PingOne data into your Power Automate tasks, you need a new SQL Server connection:

1. Log in to Power Automate
2. Click Data -> Connections -> New connection
3. Select SQL Server
4. In the connection wizard:
   
   
   • Set Authentication Type to "SQL Server Authentication"
   • Set SQL server name to the address of your Connect Server instance (connect_server_url)
   • Set SQL database name to the name of the virtual PingOne database you created earlier (like pingonedb)
   • Set the Username and Password and click Create

Integrating PingOne Data into Power Automate Tasks

With the connection to Connect Server configured, you are ready to integrate live PingOne data into your Power Automate tasks.

1. Log in to Power Automate
2. Click My flows -> New and choose to create the flow from blank or template
3. Add (or configure) a SQL Server action (like Get rows) and configure the action to connect to your Connect Server connection
4. Select a Table to work with (from the drop-down menu) and configure any advanced options (like filters, orders, etc)
5. Configure any actions to follow and test, then save the flow

SQL Access to PingOne Data from Applications

Now you have a direct connection to live PingOne data from Power Automate tasks. You can create more connections and workflows to drive business — all without replicating PingOne data.

To get SQL data access to 200+ SaaS, Big Data, and NoSQL sources directly from your applications, see the CData Connect Server.

Related Power Automate Articles

This article walks through using CData Connect Server with Power Automate (Online). Check out our other articles for more ways to work with Power Automate Desktop:

• PingOne Data in Power Automate Desktop using CData Connect
• PingOne Data in Power Automate Desktop via ODBC