Actions in Workflows
Action Types: Customizing Responses to Events
Actions are the steps that must be taken after an event occurs. All actions start with a notification to a customer endpoint and require a 200 OK
response from the customer endpoint to indicate successful delivery.
Some actions require an additional response from the customer endpoint to complete the user transaction. Others may trigger additional steps or transactions, such as automatically configuring an email sent on behalf of the customer (coming soon).
Actions can be either asynchronous (Notify) or synchronous (Enrich). Asynchronous actions, like Notify, only require notifying the target service that an event has occurred. Synchronous actions, like Enrich, require a response from the target system before the event can proceed.
For example, in the case of processing signals from an external risk engine, a response is needed to determine the appropriate action before the user journey can proceed.
One or more actions can be configured for each event type.
Action Types
The Workflows feature supports the following action types:
Action Type | Description | Execution | Configuration Options | Events Supported |
---|---|---|---|---|
Notify | Send a notification to one or more endpoints. | Asynchronous | No custom configuration at this time. Notifications will include standard data depending on the type of event. User Data Change events will include a standard set of user details. Transactional email events will include basic user data as well as a verification URL. | User Update, User Created, User Deleted, User Revoked, Pre-Registration, Registration, Forgot Password, Resend Verification |
Enrich | Send a notification to an endpoint. The customer endpoint needs to respond with data to enrich the transaction before it can proceed. | Synchronous | No custom configuration at this time. Notifications will include standard data depending on the type of event. Transactional enrich events will include limited user information. | Login |
Notify
Notify is an action type within Workflows that sends a notification to one or more endpoints when an event occurs. It allows you to configure notifications that include standard data based on the type of event. For example, User Data Change events will include a standard set of user details, while Transactional email events will include basic user data and a verification URL.
Notify actions are executed asynchronously, meaning they do not require a response from the target system to proceed with the event.
Enrich
Enrich is an action type within Workflows that allows you to send a notification to an endpoint and wait for a response from the customer endpoint to enrich the transaction. This action type is used when additional processing or data enrichment is required before the transaction can proceed.
Enrich actions are executed synchronously, meaning a response from the target system is needed before the current transaction can continue. For example, in the case of a login event, multiple steps, such as email verification, password check, and risk score assessment, can be performed through the Enrich action.
Please note that currently, there are no custom configuration options available for Notify and Enrich actions in Workflows.
The configuration options and execution details for Notify and Enrich actions provide flexibility and customization within your workflows.
Updated 12 months ago