About the elements of Okta Workflows

A Workflow, or Flow, is a sequence of steps that represent the events, logic, and actions in a use case.

Flow cards

Steps in a Flowo move from left to right, and are visually represented as cards. When you're ready turn your use case into a Flow, start thinking about the following concepts:

  • Event - What has to happen for your Flow to begin? The first card in any Flow is an Event.
  • Action - What should happen if the application event occurs? Action cards instruct your Flow to send commands to applications.
  • Function - Use cases aren't always linear. How should action cards account for different scenarios? Function cards let you act on the data from a card or branch into another logical flow.

Screenshot of the event, action, and function cards in a full flow

How does it work?

The triggering event and the resulting actions in your use case are linked through connectors and mapped input and output values.

Optional elements

  • Notes - Notes explain the Flow or set reminders. You can add them between events, actions, or functions without affecting the run-time process.
  • Templates - A template is a copy of a Flow created by Okta that fulfills a use case with minimal configuration.

Getting help

In addition to these Help Center pages, Okta Workflows is supported by in-console user documentation. The Learn site contains tutorials for your common use cases, featuring video walkthroughs and step-by-step tasks, as well as application and function reference that you can launch while you're building Flows.