Events are occurrences that trigger Flows to run. For example, a Flow would run every time an issue is created in Jira. Event cards pass data from the third-party service to the Flow in the form of drag-and-drop outputs.
There are four types of events.
Application events occur when something happens in Okta or an external application. For example:
- A user is added to an application in Okta
- A new customer is created in Salesforce
- A new row is added to a Google Sheet
Many application events, including those from Okta, are triggered in response to an incoming webhook. The external system makes an HTTP call to Workflows immediately when the specified event occurs.
Other application events check a given service for new or updated records on a recurring schedule. Most of these cards poll the connected application for new data every five minutes by default. But by using the event card options, you can change the polling schedule to a custom schedule. See Set schedule options.
Scheduled Events allow you to execute a Flow at a given interval. This type of event can be used to poll a web service for new or changed records, or to run a periodic process such as a nightly report.
On Demand Flows
On Demand Flows are executed in response to a customer or system calling an API endpoint. Within Okta, this is typically used when calling a Flow from an Inline Hook. It can also be used to invoke Flows from a third-party system that doesn't have an out-of-the-box event available in its connector.
Event cards have output fields that can be used to pass data from the event to other steps in the Flow for further action. For example, if your Flow's event is User Added to Application in Okta, then the Flow will kick off once for each user that is added to the specified application. The outputs of the Event card are assigned values based on properties of the Okta event, such as the user's username, the application name, and the time when the event happened. You can manipulate the data with built-in text, math, object and list functions and add custom logic and branching to handle different conditions through additional cards in the Flow.
Options to poll for data