Automation recipes

Each recipe below is a starting shape: the trigger to pick, the nodes to chain, and the settings that matter. For the full detail on any node, see Triggers & actions.

Birthday message

Wish contacts a happy birthday, optionally with a coupon.

1. Trigger: Birthday. Set Send timing to On the day (or a few days before, so a code arrives in time).
2. Send Email: the birthday message.

Setup: the Birthday trigger reads a contact field named Birthday that holds a full date of birth (e.g. 1990-03-15). Add it as a Date custom field, or map a birthday column when you import contacts. Contacts without that field set are simply never enrolled.

Anniversary message

Celebrate how long someone has been subscribed.

1. Trigger: Anniversary. Nothing to configure but Send timing.
2. Send Email: the anniversary message.

The Anniversary trigger uses each contact's subscribe date automatically. It first fires one year after they subscribed, not on the day itself.

A recurring custom date (renewal, "member since", policy start)

For any annual date you track yourself, other than birthday or subscribe date.

1. Create a Month & Day custom field (e.g. "Renewal Date"), stored as MM/DD. Populate it by import, API, or on the contact profile.
2. Trigger: Date Field Match → pick that field.
3. Set Send timing — commonly 30 days before for a renewal nudge.
4. Send Email.

All three date recipes share the same behavior: the email goes out around the hour set in Journey Settings → Send time for date-based triggers (default 9 AM) in the contact's own time zone, and the trigger repeats every year on its own. See Send timing for date-based triggers.

Welcome series

Introduce new subscribers over a few days.

1. Trigger: New Subscriber Joined (or Form Submitted, to scope it to one signup form).
2. Send Email: welcome / what to expect.
3. Time Delay: 2 days.
4. Send Email: your best content or a first offer.
5. (optional) Condition: Clicked previous email within 3 days → Yes/No paths for the engaged vs. the quiet.
6. Add Tag: welcomed, so you can exclude these contacts from other intro flows.

Post-purchase follow-up

Thank buyers, then ask for a review.

1. Trigger: Made a Purchase. Leave the filters empty for any order, or set a minimum value / product.
2. Send Email: order thank-you.
3. Time Delay: 7 days (chain another delay if you want longer).
4. Condition: Made a purchase within 7 days → route repeat buyers away from the review ask if you want.
5. Send Email: review request.

Abandoned cart recovery

Bring back shoppers who didn't check out.

1. Trigger: Abandoned Cart. Optionally set a minimum cart value.
2. Time Delay: a few hours.
3. Send Email: "still thinking it over?" with the cart contents.
4. Time Delay: 1 day.
5. Condition: Made a purchase within 2 days → Yes ends the flow; No continues.
6. Send Email: last nudge, optionally with an incentive.

Win-back / re-engagement

Reach contacts who've gone quiet.

1. Trigger: New Subscriber Joined — then immediately gate on engagement, or enrol contacts by adding them to a "dormant" segment and use Added to Segment as the trigger.
2. Condition: Inactive for N days (e.g. 90) → No path exits.
3. Send Email: "we miss you" / what's new.
4. Time Delay: 5 days.
5. Condition: Opened previous email within 5 days → Yes: Add Tag re-engaged. No: continue.
6. Send Email: final check-in that sets expectations about list hygiene.

Segment-entry journey

Run a flow whenever someone qualifies for a segment (e.g. becomes a VIP, crosses a spend threshold).

1. Trigger: Added to Segment → pick the segment.
2. Build the flow (e.g. Send Email a VIP perk, Add Tag vip).

Removed from Segment works the same way for the opposite case — for instance, notifying someone their VIP status lapsed, or moving them into a different nurture track.

Preference-driven journey

React when a contact updates what they want to hear about.

1. Trigger: Preference Updated. Optionally filter to one email category.
2. Send Email: content matched to the category they just opted into.

Tag-driven handoff

Use tags as the seam between automations, or between your team and an automation.

1. Trigger: Tag Added → pick the tag (e.g. demo-requested, applied by a form, the API, or a teammate).
2. Build the follow-up flow.

Pair this with an Add Tag node at the end of another journey to chain sequences: journey A finishes and tags onboarded; journey B triggers on onboarded.