You can use attributes to set your own rules for each trigger, action, or control. Here is how attributes work in automations.
By clicking the Plus Icon inside any trigger or actions, a small pop-up will appear giving you a list of attributes under 3 different tabs:
Previous Steps: Dynamic attributes passed by previously chosen Event, Condition, or API (such as Order ID, Points Earned, or Friend Name) from one node to another inside your automations. Variables here will be dependant on attributes used in the previous trigger or action.
Customer Variables: All customer-related variables such as name, ID, number, referral link, etc.
Global Variables: Variables that have to do with your general configurations, like chosen currency, points name, score name, etc.
Here is a list of attributes you will find while creating your automation:
Previous steps | Customer Variables | Global Variables |
|
|
|
Carry Over Attributes Across Automation Nodes
Dynamic attributes are passed from one node to another, such as Order ID, Points Earned, or Friend Name, from one node to another inside your automations. This enables richer personalization, smarter branching, and more context-aware automation actions.
Why This Matters
Previously, attributes generated in one node (e.g., an event or Add Points) couldn’t be reused later in the same automation. That meant messages and actions couldn’t dynamically reflect the context of the customer’s previous interactions.
Now, attributes flow seamlessly across nodes, allowing for smarter, fully contextual automation journeys.
How it works
Attribute Persistence
Attributes created or received in one node (Event, Condition, or API) are automatically available to all subsequent nodes in the same automation branch.
Attributes remain accessible for personalization in later actions.
Dynamic Variable Usage
Action nodes (e.g., Send Email, Send SMS, Assign Points) can now reference these carried-over attributes.
The variable picker in the dashboard displays available attributes grouped by source node.
Editing & Safety
If an earlier node is edited or removed, any dependent attributes trigger a warning:
“This attribute is no longer available.”
Missing attributes are safely replaced with placeholders to prevent automation errors.
Here are some examples of what you will find as a subsequent of a chosen first attribute:
Event/attribute chosen in the first Node | Subsequent variables you will find in the next nodes under "Previous Steps" |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|

