When configuring a Journey, there may be times when you want to account for an event that is not directly handled by the Alloy system, such as extending an offer to a customer or making a request to an external service. Action Nodes can be used for this purpose.
This function allows Alloy to wait on a user-specific or external service event before continuing in the Journey Application. This article details the steps for adding Action Nodes within a Journey in the Alloy dashboard.
Create the Action Node
Within the dashboard, Journey Actions can be configured by navigating to Journeys > Manage Actions > Add Action.
On the Add Action modal, complete the following:
- Enter an Action Name.
- Select End User or Service depending on the action being configured. The configuration options are the same for both.
- Decide whether the Action should expire and select Yes or No.
- If the Action should expire, set the number of days before expiration.
- Under Select Outcome, set the possible Outcomes for the Action.
- For example: Expired, Approved, Denied
- Any Outcome configured in your Alloy account can be used. There is also an option to Create New Outcome on the Add Action modal.
Action Node Configuration
Days to Expiration
Actions can optionally be configured to expire in a set amount of days. If an Action expires, the Journey Application will advance to the node to which the expired outcome for that Action is mapped. For example, an End User Action that expires can be mapped to a Denied outcome.
Add the possible Outcomes for the Action.
Once Actions have been created they can be added to a Journey by clicking the + and selecting End User Action or External Service.
For each Action Node Outcome configured, an Application Outcome must be mapped. In the below example, the Expired Action Node Outcome is mapped to the Denied Application Outcome.
While this article documents the basic steps to create Journey Action Nodes in the Alloy dashboard, please see the User Action Nodes section in the Alloy Developer documentation for the technical integration requirements and additional context on this feature.