Skip to main content

Workflow Templates

Nine reference flows. Match a use case to a template and copy its shape on whichever surface you author on (Dashboard or Framework). Each template includes a metadata table: Channels noted with (if channel is configured) are only included when the organization has that integration set up. Steps with a Step condition line run only when the condition holds — see step-conditions.md for the JSON-Logic and Framework skip equivalents.

1. Order Confirmation


2. Comment on Your Post


3. Payment Failed


4. Account Suspended

Critical workflow:
  • Bypasses subscriber preferences
  • No delays, immediate delivery
  • All available channels in parallel

5. Forgot Password

No In-App step — the user isn’t signed in when this fires.

6. Trial Expiring Tomorrow


7. Explicit Channel Request (User-Specified)

User said: “Create a push notification when order ships”
Rule: when the user names channels, use only those channels. No fallbacks. No extras. Add the channel even if it’s not configured in the organization (the user explicitly asked for it).

8. Webhook / External API Call

User said: “Notify users and call our webhook when a payment fails”
Use HTTP Request whenever a workflow must call an external API or webhook in addition to (or instead of) sending notifications.

9. Fetch Data Then Notify (HTTP Step → Channel Step)

User said: “Fetch the user’s plan from our API and send them a personalized email”
Rule: when a subsequent step references HTTP response data, the HTTP step must declare a responseBodySchema. Only properties declared in the schema are addressable as {{ steps.<http-step-id>.<property> }}.

See Also