Integrate Okta Data into Power Automate Desktop using CData Connect

Jerod Johnson
Jerod Johnson
Director, Technology Evangelism
CData Connect for Okta Data enables you to integrate Okta data into workflows built using Microsoft Power Automate Desktop.

CData Connect enables you to access live Okta data in workflow automation tools like Power Automate. This article shows how to integrate Okta data into a simple workflow, saving Okta data into a CSV file.

CData Connect provides a live interface for Okta, allowing you to integrate with live Okta data in Power Automate — without replicating the data. Connect uses optimized data processing out of the box to push all supported SQL operations (filters, JOINs, etc) directly to Okta, leveraging server-side processing to quickly return Okta data.

Configure Okta Connectivity for Power Automate

Connectivity to Okta from Power Automate is made possible through CData Connect AI. To work with Okta data from Power Automate, we start by creating and configuring a Okta connection.

  1. Log into Connect AI, click Sources, and then click Add Connection
  2. Adding a Connection
  3. Select "Okta" from the Add Connection panel
  4. Selecting a data source
  5. Enter the necessary authentication properties to connect to Okta.

    To connect to Okta, set the Domain connection string property to your Okta domain.

    You will use OAuth to authenticate with Okta, so you need to create a custom OAuth application.

    Creating a Custom OAuth Application

    From your Okta account:

    1. Sign in to your Okta developer edition organization with your administrator account.
    2. In the Admin Console, go to Applications > Applications.
    3. Click Create App Integration.
    4. For the Sign-in method, select OIDC - OpenID Connect.
    5. For Application type, choose Web Application.
    6. Enter a name for your custom application.
    7. Set the Grant Type to Authorization Code. If you want the token to be automatically refreshed, also check Refresh Token.
    8. Set the callback URL:
      • For desktop applications and headless machines, use http://localhost:33333 or another port number of your choice. The URI you set here becomes the CallbackURL property.
      • For web applications, set the callback URL to a trusted redirect URL. This URL is the web location the user returns to with the token that verifies that your application has been granted access.
    9. In the Assignments section, either select Limit access to selected groups and add a group, or skip group assignment for now.
    10. Save the OAuth application.
    11. The application's Client Id and Client Secret are displayed on the application's General tab. Record these for future use. You will use the Client Id to set the OAuthClientId and the Client Secret to set the OAuthClientSecret.
    12. Check the Assignments tab to confirm that all users who must access the application are assigned to the application.
    13. On the Okta API Scopes tab, select the scopes you wish to grant to the OAuth application. These scopes determine the data that the app has permission to read, so a scope for a particular view must be granted for the driver to have permission to query that view. To confirm the scopes required for each view, see the view-specific pages in Data Model < Views in the Help documentation.
    Configuring a connection (Salesforce is shown)
  6. Click Save & Test
  7. Navigate to the Permissions tab in the Add Okta Connection page and update the User-based permissions. Updating permissions

Add a Personal Access Token

When connecting to Connect AI through the REST API, the OData API, or the Virtual SQL Server, a Personal Access Token (PAT) is used to authenticate the connection to Connect AI. It is best practice to create a separate PAT for each service to maintain granularity of access.

  1. Click on the Gear icon () at the top right of the Connect AI app to open the settings page.
  2. On the Settings page, go to the Access Tokens section and click Create PAT.
  3. Give the PAT a name and click Create. Creating a new PAT
  4. The personal access token is only visible at creation, so be sure to copy it and store it securely for future use.

With the connection configured and a PAT generated, you are ready to connect to Okta data from Power Automate Desktop.

Integrate Okta Data into Power Automate Workflows

After configuring CData Connect with Okta, you are ready to integrate Okta 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 options to connect to Okta, query Okta using SQL, and write the query results to a CSV document.

Add an Open SQL Connection Action

Add an "Open SQL connection" action (Action -> Database) and click the option to build the Connection string. In the Data Link Properties wizard:

  1. On the Provider tab: select Microsoft OLE DB Driver for SQL Server
  2. On the Connection tab:
    1. Select or enter a server name: set to tds.cdata.com,14333
    2. Enter information to lag onto the server: select "Use a specific username and password"
      • Set User name to your CData Connect AI user name (e.g. [email protected])
      • Set Password to your PAT
      • Select the database: use the database configured above (e.g. Okta1)
  3. Click "Test Connection" to ensure the connection is configured properly
  4. Click "OK" A configured connection to CData Connect

After building the connection string in the Data Link Properties wizard, save the action.

A configured

Add an Execute SQL Statement Action

Add an "Execute SQL statement" action (Action -> 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 Users

After configuring the properties, save the action.

A configured

Add a Write to CSV File Action

Add a "Write to CSV file" action (Action -> 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.

A configured

Add a Close SQL Connection Action

Add a "Close SQL connection" action (Action -> Database) and configure the properties.

  • SQL Connection: %SQLConnection% (the variable from the "Open SQL connection" action above)

After configuring the properties, save the action.

A configured

Save & Run the Flow

Once you have configured all the options 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 save Okta data into a CSV file.

Application data in a CSV file (Salesforce is shown)

With CData Connect AI, you get live connectivity to Okta data within your Microsoft Power Automate workflows.

SQL Access to Okta Data from Cloud Applications

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

To get SQL data access to hundreds of SaaS, Big Data, and NoSQL sources directly from your cloud applications, sign up for a free trial of CData Connect AI.

Related Power Automate Articles

This article explains how to use CData Connect AI with Power Automate Desktop. Check out our other articles for more ways to work with Power Automate (Desktop & Online):

Ready to get started?

Learn more about CData Connect AI or sign up for free trial access:

Free Trial