Triggers & actions
Every trigger, action, and condition node available in the journey builder.
Trigger node
Every journey starts with one Trigger Event:
| Trigger | Extra configuration |
|---|---|
| New Subscriber Joined | — |
| Made a Purchase (Shopify/WooCommerce) | Store selector, optional min. order value, optional product/collection filter; leave fields empty to trigger on any purchase |
| Abandoned Cart (Shopify/WooCommerce) | Store selector, optional min. cart value |
| Tag Added / Tag Removed | Pick one or more tags |
| Added to Segment / Removed from Segment | Pick a segment |
| Form Submitted | Pick a published form |
| Birthday | Send timing (see below). Reads a contact field named Birthday holding a full date of birth (e.g. 1990-03-15); create it as a Date custom field or map a birthday column on import. Feb 29 birthdays fire on Feb 28 in non-leap years. |
| Anniversary | Send timing (see below). Fires each year on the anniversary of the contact's subscribe date. Nothing to pick. The first-year date (the day they subscribed) doesn't count; it starts the next year. |
| Date Field Match | Pick any Month & Day (custom field, stored as MM/DD), with a shortcut to create one. Use it for renewal dates, "customer since," policy start dates, appointments — anything recurring on a month/day. Send timing (see below). |
| Preference Updated | Optional filter by email category |
Purchase triggers need a connected store
"Made a Purchase" and "Abandoned Cart" only appear once Shopify or WooCommerce is connected. See Connecting your store.
Send timing for date-based triggers
Birthday, Anniversary, and Date Field Match all share one Send timing control:
- On the day, 1–90 day(s) before, or 1–90 day(s) after the date.
- The send goes out around the hour set in Journey Settings → Send time for date-based triggers (default 9 AM), in each contact's own time zone — or your workspace time zone if the contact has none.
- The trigger repeats automatically every year, once per contact per occurrence. The journey's re-enrollment policy does not apply to date triggers.
- One date-based trigger per automation. To send at more than one offset (say, a heads-up a week before and a message on the day), start the journey at the earliest offset and use Time Delay steps to reach the later ones, or build a separate automation per offset.
Send Email node
Configure the email three ways:
- Start from Template: pick from the same built-in template set used in Broadcasts.
- Use Existing Broadcast: copy the content of another broadcast — one that's been sent, is currently sending, or is still a draft.
- Start Blank: opens the full block editor with a default logo + heading.
Once set, the node shows a subject/preview card with Edit Email and Replace buttons. It uses the same canvas as broadcasts; see The email builder. A contact who's unsubscribed or been suppressed since enrolling is automatically skipped at this step rather than emailed anyway.
Time Delay node
Set a Wait Pattern: a numeric amount plus Minutes, Hours, or Days. Subscribers pause at this node for exactly that long before continuing. (Delays are capped at 7 days per individual wait step; chain multiple waits for longer pauses.)
Condition node
Splits the journey into Yes and No paths based on a Logic Rule:
| Rule | Extra fields |
|---|---|
| Opened previous email / Clicked previous email | Within N days |
| Clicked specific link | Link URL (or partial match) + within N days |
| Made a purchase | Within N days |
| Has specific tag | Pick one or more tags |
| Is in segment / Is NOT in segment | Pick one or more segments |
| Open rate is above % | Threshold % |
| Inactive for N days | Days inactive |
| Custom field equals | Field, operator (equals / does not equal / greater than / ≥ / less than / ≤), and a value; for equals/not-equals you can enter multiple comma-separated values at once |
A/B Split node
Randomly routes contacts down one of several weighted branches, useful for testing different journey paths, not just different email content.
Add Tag node
Choose Add tags or Remove tags, then pick which ones. A simple, common way to mark where a contact is in your funnel (e.g. tag welcomed at the end of a welcome series so they're excluded from re-entering it).
Combine tags with re-entry rules
Since re-enrollment defaults to Never, an Add Tag node isn't required to prevent someone from re-entering the same journey, but it's useful for driving other automations or segments off of "has completed X flow."