Okta Workflows is a no-code platform that enables you to automate business processes and customize your identity-related use cases.
With Okta Workflows, you can:
- Provision and deprovision app accounts. When an employee joins your company, Okta Workflows can automatically create their identity in your apps, as well as set entitlements, assign folder shares, and send a message to their manager. When an employee leaves your company, Okta Workflows can freeze the account, transfer their digital assets to a manager, and then deactivate the user account three days later.
- Sequence actions with logic and timing. Okta Workflows can create deactivated accounts in all apps one week before a new employee's start date, and then activate them on their first day. When an employee leaves your company, Okta Workflows can remove access to all apps except payroll, and then remove that access after one year.
- Resolve identity creation conflicts. Okta Workflows can host logic that detects username conflicts and generates unique usernames.
- Respond to security incidents. When Okta detects a suspicious sign-in, Okta Workflows can notify your security team through PagerDuty or create a ticket in ServiceNow.
- Log and share lifecycle events. Okta Workflows can query Okta APIs and syslog events, run logic, and compile data into a CSV file. Then, Okta Workflows can email that file to your teams.
Access this feature
In the Admin Console, go to Workflow > Workflows console.
You must be a Super Admin in your org to access Okta Workflows.
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.
A Workflow, or Flow, is a sequence of steps that represent the events, logic, and actions in a use case. These steps move from left to right in the Workflows console, 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.
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.
- 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 app (for example, admin 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.