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.
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.
The triggering event and the resulting actions in your use case are linked through connectors and mapped input and output values.
- Connector - Which applications are involved in your Flow? Connectors enable you to interact with them without setting up APIs.
- Connection - A connection is your unique level of access to the connected 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. (for example, 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. or end user).
- Input - Input fields determine how an action or function card proceeds. For example, the input field of the Search for User action card above is User Details.
- Output - Output fields contain the results that are generated by the event, action, or function card. In the example Flow above, the User Unassigned from Application event card produces output values like Date and Time, Message, Event ID, Event Type, and Event Time.
- Mapping - The movement of data between cards is referred to as mapping. To map data between cards, drag and drop the output field of one card to the input field of another card. Be sure that the format of the fields match (text, number, true/false, date & time, object, or list).
- 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.
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.Top