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.
- Workflows
- Okta Event cards
To run an Okta event-triggered workflow manually, any fields from the event card that are used in the workflow need to be manually entered in the dialog that is 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 entered to properly test the flow. Note that 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:
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 the department attribute of a user and the flow will trigger. 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:
