Recipes

A recipe for every lifecycle outcome

Each one is a working flow built from a few primitives — from a welcome series to human-approval gates and agent-driven sends. Pick the outcome; the recipe shows the code.

Start here — the four modes

Transactional emails

Fire a single email from your app code on a server-side event — receipts, password resets, magic links.

Lifecycle journeys

Multi-step sequences that wait, branch on behaviour, and exit themselves — welcome series, trial nudges, win-backs.

Marketing campaigns

Send a one-off broadcast to an audience, with preferences and unsubscribe handled for you.

Events & contacts

Push events and upsert contacts from anywhere, then trigger journeys and buckets off the stream.

8 recipes

Onboarding & activation

Get new signups to the first moment of value — and react to whether they got there.

Open category

Welcome series

Greet on signup, resume the instant they activate, and nudge only the ones who don't.

See the code

Activation milestones

Walk setup step by step and nudge only the milestone the user is actually stuck on.

See the code

Waitlist to launch

Code-defined membership, an idempotent launch broadcast, and a chase journey for non-activators.

See the code

Verification chase

Send the verify-email transactionally, then chase it with two re-sends that stop the instant the token is redeemed.

See the code

Welcome new Discord members

On a Discord join, wait for the member to link an email — then welcome them, or nudge the unlinked in-channel.

See the code

Link a Discord account to an email

Attach an email to a Discord account with an in-Discord /link command that emails a one-click confirm link, then branch journeys on whether a contact is linked.

See the code

Welcome new Telegram members

Reply on a bare /start with a welcome, and echo every inbound message — an inbound Telegram event becomes an outbound reply from a journey.

See the code

Link a Telegram account to an email

Attach an email to a Telegram account with a /link email-confirm flow (or a one-tap /start deep link), then read the linked contact in a journey.

See the code

4 recipes

Trial, billing & upgrades

Trial arcs, dunning, and upgrade nudges that stop the moment money arrives.

Open category

Trial conversion sequence

A day-1 value email, a usage branch mid-trial, a bucket-timed T-3 push — gone the instant they pay.

See the code

Failed payment dunning

Notify, wait through Stripe's retries, escalate twice, and stop the instant the invoice is paid.

See the code

Usage limit upgrade

Nudge at 80%, escalate only at the wall, and stop the instant they upgrade.

See the code

Cancellation save

Ask why with three one-tap links, branch on the answer, and stop the moment they reactivate.

See the code

4 recipes

E-commerce

Carts, orders, deliveries, and restocks — purchase-stream flows end to end.

Open category

Abandoned cart recovery

Wait for the purchase, remind twice, and stop the instant the order lands.

See the code

Post-purchase series

Receipt, a durable wait for delivery, product onboarding, and a hand-off to the review ask.

See the code

Review request

Five stars in the email, a durable wait for the rating, and a branch on the score.

See the code

Back-in-stock notifications

Per-product opt-in lists, a signed restock webhook, and an idempotent one-shot broadcast.

See the code

5 recipes

Retention & engagement

Win-backs, surveys, digests, and the sunset policy that protects deliverability.

Open category

Win-back and sunset

Try to win dormant users back, then turn sustained silence into a clean unsubscribe.

See the code

NPS survey

Score bands answered inside the email, detractors flagged to a human, promoters asked for a referral.

See the code

Weekly digest

One ctx.digest() call collapses a week of activity into one email — replay-safe, no idempotency bookkeeping.

See the code

Anniversary emails

One celebration per year, gated on recent activity, landing at 09:00 local time.

See the code

Re-engage quiet Discord members

Read the derived last_seen on a contact, find members quiet for 30 days, and email a win-back.

See the code

2 recipes

Timing & scheduling

Send at the right moment in each person's own timezone — reminders, anniversaries, and time-of-day windows.

Open category

Timezone-aware scheduling

Turn 'next Tuesday at 9am, their time' into a Date and sleep durably until it.

See the code

Event reminder sequence

T-24h and T-1h reminders computed from the event's own start time, then replay vs thanks.

See the code

5 recipes

Human-in-the-loop

Flows that pause for a person — approvals, lead alerts, concierge touches.

Open category

Lead alerts

A confirmed hand-raise pages a human — outside the journey's exit rules and the lead's preferences.

See the code

Human approval gate

Park the journey on a durable wait until an operator approves with one event — silence fails safe.

See the code

Concierge onboarding

Page a CSM on enterprise signup, park until they confirm contact, and fall back so the customer never stalls.

See the code

Support follow-up

A next-morning 'did this fix it?' — yes ends quietly, no fires a reopen event and pages support.

See the code

Route a Discord reaction as a signal

A specific reaction becomes a hand-raise — filtered at enrollment, flagged for a human to follow up.

See the code

3 recipes

Agents & AI

Agents as producers and consumers of the same event stream your app uses.

Open category

Agent-triggered journeys

An agent is just another producer — same events, same journeys, with guards on its output.

See the code

AI-drafted sends

The model fills typed prop slots; the template, footer, and tracking stay code-owned.

See the code

Agent feedback loop

Email answers reach your agent over a signed webhook; its verdict steers the parked journey.

See the code

4 recipes

Pipelines & orchestration

Webhook sources in, destinations out, and journeys composed into funnels.

Open category

PostHog-triggered journeys

Forward identified PostHog events into journeys — with the guards that keep echoes and anonymous noise out.

See the code

Cross-journey funnels

One journey routes into others with eligibility events — every branch keeps its own guards and kill switch.

See the code

Lifecycle alerts in Slack

One filtered destination decides which lifecycle moments page a human — journeys never touch Slack.

See the code

Discord engagement alerts in a channel

One filtered destination decides which lifecycle moments post to a Discord channel — journeys never touch Discord.

See the code

The primitives behind them

Journeys Buckets Email Semantic links Webhook sources Destinations

Start cooking

Every recipe is a file in your repo

Read them end to end in the docs, or scaffold an app and start from a working flow.

Browse recipes in the docs Get started