Flow templates

Pre-built flows for common subscription lifecycle moments.

#What a template is

A flow template is a pre-wired, contract-valid FlowIR — a complete graph of entry, delay, message, and exit nodes assembled around a common subscription lifecycle pattern. Opening a template in the builder gives you a working flow you can edit and activate without starting from a blank canvas.

Each template is tagged with a growth goal and carries a trigger label derived from its entry node. Every call to open a template mints fresh node and flow IDs, so re-opening the same template never collides with a previous draft.

#Goals

Templates are grouped by growth goal:

Goal	Typical use case
Activation	Turn a new install or sign-up into a first meaningful action.
Conversion	Move a trial or free user to a paid subscription.
Retention	Keep active users engaged and protect hard-won habits.
Win-back	Re-engage a user who has gone quiet or churned.
Monetization	Surface upgrade offers, upsells, or premium feature awareness.

The goal determines the accent colour on the gallery card and groups templates in the picker.

#Trigger types used in templates

Templates use three entry trigger types:

Trigger	When the flow starts
Event (on <event_name>)	Fires when a named event arrives for the user. Templates that stop on conversion set an exit criterion (e.g. subscription_started) so users who convert are not sent the remaining pushes.
Inactivity (after Nd)	Fires after a configurable period of no app-open. Used for win-back sequences.
Schedule (cron UTC)	Fires on a UTC cron expression. Used for time-based campaigns such as an annual Wrapped reveal. Re-entry is forced to multiple.

Note

The trigger label shown on each gallery card ("on trial_started", "after 7d inactivity", "cron 0 8 27 11 *") is derived at runtime from the entry node's trigger definition, so it always stays in sync with the actual IR.

#How to use a template

Open Flows in the sidebar and click New flow.
Choose Browse templates to open the gallery. Cards show the goal pill, trigger label, and push count for each template.
Click a card to open the template in the builder. A fresh copy of the FlowIR is instantiated — no shared state with the gallery.
Edit any node: update message copy, adjust delays, add or remove branches, change the trigger event name to match your event catalogue.
Click Save & activate when ready. The flow goes through the same validator used by the AI builder; errors block activation.

Heads up

Message copy in templates uses placeholder variables in two formats. Known chip variables ({{ first_name }}, {{ days_left }}, {{ plan }}, {{ country }}, {{ lifetime_value }}) are interpolated automatically. Text in [square brackets] is literal — replace it with your own values before activating.

#Push count

The gallery card shows the number of Message nodes in the template. This count is computed from the built IR each time (not hardcoded), so it stays accurate if a template is updated. A flow with more steps is not necessarily better — a tight 3-push win-back often outperforms an exhaustive 10-push escalation.

#Re-entry and exit criteria in templates

Templates set sensible defaults for re-entry:

Re-entry policy	When it appears
Once	Most activation and conversion sequences — a user should not repeat the onboarding journey.
Multiple	Recurring engagement flows and scheduled campaigns — users can re-enter on each trigger occurrence.
Cooldown (7 days)	Recovery flows triggered by repeatable events (e.g. cart_abandoned) — prevents spamming if the same event fires again quickly.

Exit criteria are set on templates where a conversion event makes the remaining steps irrelevant. Adjust them to match the event names in your own catalogue.

#Building from scratch vs templates

Quick comparison

Template  → Pre-wired graph, sensible defaults, ready to edit.
              Best for: known patterns (trial conversion, win-back,
              habit loops). Edit the copy and event names; activate.

Blank canvas → Full control. Use the AI prompt bar to scaffold a
              first draft, or drop nodes one at a time.
              Best for: custom logic, multi-branch experiments,
              unusual trigger combinations.

AI generation → Describe the flow in plain English. The model
              generates a validated draft for your review.
              Best for: quick prototyping, translating a
              specification into a working flow.

Next: Notification templates — a library of push copy starters you can drop into any message node.