Build and test a Flow

This Early Adopter Program feature is available to selected customers only. If you're interested in participating in Okta Workflows EAP, ask your Customer Success Manager to check for availability.


Use the drag-and-drop interface in the Workflows console to build your own Flows. Each event and action in a Flow works with a pre-built connector, which allows you to communicate with other applications without code or APIs. Simply connect your applications, specify the event and actions, and fill in the details.


Before you begin


Build a Flow

This procedure covers the basic sequence of commands to build a Flow. After you learn the mechanics, try building some Flows for real-world use cases.

  1. In AdminAn abbreviation of administrator. This is the individual(s) who have access to the Okta Administrator Dashboard. They control the provisioning and deprovisioning of end users, the assigning of apps, the resetting of passwords, and the overall end user experience. Only administrators have the Administration button on the upper right side of the My Applications page. Console, go to Workflow > Workflows console.
  2. In Workflows console, click New Flow.
  3. In the first card, click Add Event.
  4. Pick the appAn abbreviation of application. Essentially, it is a web-based site used to perform any number of specific tasks, and requires authentication from end users by signing in. where the event will occur, and then select from its available events.
    • If you haven't connected the app yet, click New Connection and enter the required information. App-specific help is available in this window by clicking Need help?.
    • If you've already connected the app but you have multiple accounts, select the one that you want to use.
  5. In the second card, click App Action or Function.
    • App Action cards send a command to an application. Pick the app where the action will occur, and then select from its available actions (if you haven't connected the app yet, you're prompted to do so). Action-specific help is available in the console by clicking .
    • Function cards act on the data from a card or branch into another logical flow. You can choose a logic function, like branching or error handling, or you can choose a function that manipulates data, like a compose card, a list, or a table. You can even choose advanced functions that make HTTP requests or parse JSON strings. Remember, though: you don't pick an app for a function card. Function-specific help is available in the console by clicking .
  6. Use the Add Another menu to add more actions, functions, or notes to your Flow.
  7. Map the data between cards. Drag the output from one card and drop it in the input of another card. Be sure that the field types match.
  8. Note: While you're building a Flow, you can test any card by clicking . Testing individual cards is a good way to ensure that your mappings work.

  9. Click . If you haven't named your Flow yet, you can do so here.
  10. Or, if you want to manually test your Flow, click the Save and Test option from the Add Another menu.



Test your Flow

There are two ways to test a Flow: you can manually enter data into the event card, or you can trigger the event in the app itself. If you chose the Save and Test menu option above, proceed to Step 2 of the manual method.

Note: It takes about 60 seconds for the flow to enable. After saving and turning on your flow, wait one minute before you attempt to trigger it.

Manually enter data

  1. In the Workflows console, click .
  2. In the Check for new data window, manually enter test data into the card fields.
  3. Click Test. The console view displays the progress of the Flow. A check mark appears in the name field of each successfully executed card.
  4. If the flow encounters an error, check the details and then click Back to Flow to make corrections.

Trigger the Flow in the app

  1. In the Workflows console, toggle Flow is OFF to ON.
  2. In your Okta instance, perform the action described in the event card.
    • If your event occurs in Okta, use your Admin Console to perform the action that will trigger the Flow. For example, if your Flow runs whenever a user is assigned to Salesforce, go to Applications > Applications, and assign a test user to Salesforce.
    • If your event is in another application, go to your home page, and then launch the app. Trigger the event there.
  3. Return to the Workflows console to view the progress of the Flow. A check mark appears in the name field of each successfully executed card.
  4. If the flow encounters an error, check the details and then click Back to Flow to make corrections.


Flow History

Check Flow History for a log of all of the times your Flow has run in the past 30 days. You can sort the Flow History pane by completed Flows and those still in progress.

When you select a record from Flow History, the full execution of the Flow appears in the Workflows console.

  • The results, duration, and time of the Flow are explained in the Execution Details window.
  • Input and output fields are populated, and the duration of time it took to successfully execute each card appears beneath a green check mark.
  • If the flow stopped, the card containing the invalid data is marked with an error.
  • If other applications supplied raw error details, that information is included for debugging purposes.
  • If you immediately triggered the Flow after turning it on, you may not see it in Flow History. Wait 60 seconds before you try it again.

Related Topics

Okta Workflows

Connect your applications

Use case tutorials

Top