Workflow Components
To understand how Workflows work, it's important to familiarize yourself with the different components involved. Workflows consist of the following components:
Component | Description |
|---|---|
Sources | Sources are where events originate. Examples are Next Identity, Akamai Identity Cloud, or a user directory. |
Events | Events serve as triggers for workflows. They represent specific transactions or occurrences, such as a user successfully logging in, resetting their password, or revoking an application's access to their data. |
Actions | Actions are what needs to be done after an event occurs. Common actions include notifying an endpoint or sending an email or SMS. Actions can be asynchronous (Action Type: Notify) or synchronous (Action Type: Enrich). |
Notifications | Notifications are the messages that are sent to targets as a result of the actions taken within workflows. The content of notifications may vary depending on the event type and the specific action being performed. |
Targets | Targets represent URL endpoints or Next Identity Connect integrations that receive and process notifications from workflows. |
Responses | Responses are sent by targets after processing the notifications received from workflows. Depending on the action type, responses can be in the form of HTTP response codes or payloads. |
Understanding how these components interact and collaborate within workflows is essential for building effective and customized automation solutions. Within this guide, we invite you to explore each component in more detail through dedicated sections. Discover how to configure and utilize them to achieve your desired workflow behavior.