How to Manually Run a Workflow that Is Triggered by Using an Okta Event Card
Last Updated:
Overview
When a workflow that uses an Okta Event card is triggered, the event data is passed to the flow and is available in the Output section of the event card. This data is typically used by other cards in the workflow for implementing conditional logic and executing other action cards. When running an event-triggered flow manually by clicking the Run button, the flow execution does not have this contextual event data, so it must be entered manually to properly test the flow.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Workflows
- Okta Event Cards
Solution
What is the process to manually run an Okta event-triggered workflow?
To run an Okta event-triggered workflow manually, any fields from the event card used in the workflow must be entered in the dialog displayed after clicking the Run button. In this example, the Changed Attributes and Okta User ID fields are mapped from the User Okta Profile Updated event card into other cards in the workflow:
When running the flow manually by clicking the Run button, these inputs must be provided to properly test it.
NOTE: The Okta User field is a JSON object and must be formatted as an object that includes the key/value pair for each of the attributes being used:
How to determine the structure of the data that needs to be populated into the respective fields?
For object fields, an easy way to determine the object structure is to perform the action described in the event card, then load the execution history and view the Output section of the event card. For the above example, use the Okta Admin console to update a user's department attribute, and the flow will be triggered. When viewing the execution history, expand each of the individual objects to see the JSON or expand the Event Details object to see the complete JSON payload for the event:
