Nodes in Stampede are the steps following a trigger in a workflow, directing actions like sending messages, waiting, or checking conditions. Types include Action Nodes (immediate actions), Condition Nodes (check guest status), Event Nodes (delays for event completion), and End/Test Nodes (finish or simulate workflows). Nodes add flexibility, creating personalized, adaptive customer journeys.
What is a Node?
If the trigger is the spark that starts your workflow, nodes are the steps that follow. Each node tells Stampede what to do next, whether that’s sending a message, waiting a few days, or checking if certain conditions are met.
Nodes let you build out a journey that feels personal and well-timed, rather than a one-size-fits-all message.
Types of Nodes in Stampede
Here are the main node types you’ll use:
Action Nodes → Do something right away (send an email, add loyalty points, tag a guest, wait).
Condition Nodes → Check for conditions (e.g. has the guest opened the last email? Do they have a “VIP” tag?).
Event Nodes → Add a delay to the system to give the customer time to complete an event. (e.g. wait 24 hours to see if the customer has opened an email/created a booking/logged into the Wifi).
End Nodes & Test → Finish the workflow, either successfully or unsuccessfully. The Test Node can be added before closing the workflow to simulate before making it live.
Why Nodes Matter
Nodes give your workflows flexibility and depth. They’re what turn a simple “trigger → action” automation into a full journey that adapts to your guests’ behaviour.
👉 Want to see how triggers and nodes work together? Check out our Example Workflows article for real-life use cases.