Examples

Lifecycle flows you can ship in an afternoon.

Real, end-to-end examples of behavior-triggered email, from the event you track in your product to the message that lands in the user's inbox. Each one is a working pattern, not a hypothetical.

Patterns

Eight flows, start to finish.

From the event you track to the message that lands in the inbox. Every flow below runs in GetFluxly today, not a hypothetical.

Onboarding

Welcome → first project nudge → activation celebration.

The day-zero sequence every SaaS needs. A static welcome on sign-up, then a behavior-aware follow-up that only fires if the user hasn't created a project after 3 days.

user_signed_up welcome wait 3d / project_created first-project nudge

3 emails 1 branch 3-day window

Activation

Stalled at step 2 of setup → contextual help email.

Track each step of your onboarding checklist. If a user gets stuck on the same step for more than 24h, send a how-to email that's specific to that step, not a generic "need help?".

setup_step_completed (n=2) wait 24h / step_completed (n=3) step-2 help guide

1 email per-step segment 24h timeout

Trial

Trial ending in 3 days → branch on engagement.

A user finishing trial gets one of two emails: highly-engaged users see a "ready to upgrade" message; low-engagement users see a "let us extend it" save offer.

trial_ends_in: 3d if events_30d > 50 upgrade now / extend trial

2 emails 1 branch revenue path

Retention

Power-feature drop-off → personal check-in.

Identify your "habit-forming" event (e.g. report_exported). When a previously-active user goes 14 days without it, send a check-in from the founder, not a marketing template.

report_exported (12 wk avg) 14d silence founder check-in

1 email from founder 14-day window

Win-back

Cancelled subscription → 30-day win-back sequence.

A 3-email sequence after cancellation: ask why (week 1), share what shipped since (week 2), offer a discount or comeback path (week 4). Exits if the user re-subscribes.

subscription_cancelled why-did-you-leave what's new come back offer

3 emails exit on resubscribe 30 days

Transactional

Receipt + post-purchase activation in one flow.

Send the receipt immediately on order_placed. Then wait 7 days; if the customer hasn't returned to the app, send a post-purchase nudge with their order context inline.

order_placed receipt wait 7d / app_visited come-back-and-use-it

2 emails instant + delayed order context

Onboarding

Team invite waiting → solo-user nudge.

You signed up but haven't invited a teammate after 5 days. For B2B products this is one of the strongest activation predictors; a small in-context nudge does the work.

user_signed_up 5d / teammate_invited invite-your-team

1 email B2B activation 5-day window

Retention

Pricing page revisit → upgrade nudge with the plan they viewed.

If a paid user views a higher-tier pricing page twice in a week, send an upgrade email tailored to that exact tier: pre-filled CTA, plan-specific features.

pricing_viewed (tier=team) ≥ 2 trait: plan = "starter" team-tier upgrade

1 email revenue path tier-specific

Missing a flow?

Send us your scenario.

Need an example for your stack? Ask and we'll write it and add it here. The patterns we publish come from real teams.

Start your trial Email a scenario