Stampede
Product reference · Workflows

Triggers

A workflow begins when something happens: a booking is made, a birthday is coming up, a guest connects to the Wi-Fi, or a guest enters an audience.

~2 min read

When you'd use it

To decide what event should start a journey.

How it behaves

Triggers are real things guests do: a booking made, completed, cancelled or no-showed, a Wi-Fi sign-in, a review left, an online or in-venue order, a loyalty signup or points earned, a form submission, or an upcoming birthday. The event starts the journey on its own.

Many triggers can be narrowed with conditions, so a workflow only starts for the cases you care about: a booking of a certain type or party size, an order over an amount or with a particular item, a review with a given rating or sentiment, or a birthday a set number of days away. A saved audience can also push guests in, and a webhook can start a workflow from an external system with your own conditions.

For groups, cross-venue triggers start a journey from a booking or form at any venue in the estate. Workflows run off live events, so a cancelled booking or a Wi-Fi sign-in starts the journey right away; birthdays are checked on a daily run so the message lands with time to spare.

Configuration and options

Booking events
Created, completed, cancelled, no-show, and last-booked.
Order and review
An online or in-venue order, or a review left.
Loyalty and Wi-Fi
A loyalty signup or points, or a Wi-Fi sign-in.
Form and birthday
A form submission, or an upcoming birthday.
Conditions
Narrow a trigger by type, amount, rating, timing and more.
Audience and webhook
A saved audience, or an external system via webhook.

Good to know

  • The available triggers depend on which modules are connected.

  • Real-time events fire immediately; birthdays run on a daily check.

  • Cross-venue triggers cover a booking or form at any venue in a group.

Frequently asked questions