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:
FieldMeaning
SeverityLOW / MEDIUM / HIGH / unset (None)
Criticaltrue ⇒ bypass preferences, skip digest, immediate delivery
ActionableInformational (no action) or Requires Action (CTA)
InteractionUSER TRANSACTION, CONVERSATIONAL, SYSTEM TRANSACTION, LIFECYCLE
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

SeverityNone
Criticalfalse
ActionableInformational
InteractionUSER TRANSACTION
Trigger
  ↓
Digest: type "regular", look-back 5min, digest time 1h
  Key: subscriberId
  ↓
In-App
  ↓
Email
  ↓
Push (if channel is configured)
  Step condition: Send only if subscriber is offline

​
2. Comment on Your Post

SeverityNone
Criticalfalse
ActionableInformational
InteractionCONVERSATIONAL
Trigger (event: payload.threadId: "post_123")
  ↓
Digest: type "regular", look-back 5min, digest time 1h
  Key: subscriberId + threadId
  ↓
In-App
  Redirect: → thread
  ↓
Push (if channel is configured)
  Step condition: Send only if subscriber is offline
  ↓
Delay (4 hours)
  Step condition: Only if In-App not seen
  ↓
Email
  Content: summary of the comments
  Step condition: Only if In-App not seen

​
3. Payment Failed

SeverityHIGH
Criticalfalse
ActionableRequires Action
InteractionUSER TRANSACTION
Trigger
  ↓
In-App
  ↓
Chat (if channel is configured)
  ↓
Email
  ↓
Push (if channel is configured)
  Step condition: Send only if subscriber is offline

​
4. Account Suspended

SeverityHIGH
Criticaltrue
ActionableRequires Action
InteractionSYSTEM TRANSACTION
Critical workflow:
  • Bypasses subscriber preferences
  • No delays, immediate delivery
  • All available channels in parallel
Trigger (event: payload.account.suspended, payload.reason: "kyc_required")
  ↓
In-App
  ↓
Email
  ↓
SMS (if channel is configured)
  ↓
Chat (if channel is configured)
  ↓
Push (if channel is configured)
  Step condition: Send only if subscriber is offline

​
5. Forgot Password

SeverityNone
Criticaltrue
ActionableRequires Action
InteractionSYSTEM TRANSACTION
No In-App step — the user isn’t signed in when this fires. 
Trigger
  ↓
Email
  ↓
SMS (if channel is configured)

​
6. Trial Expiring Tomorrow

SeverityHIGH
Criticalfalse
ActionableRequires Action
InteractionLIFECYCLE
Trigger
  ↓
In-App
  ↓
Chat (if channel is configured)
  ↓
Email
  ↓
Push (if channel is configured)
  Step condition: Send only if subscriber is offline

​
7. Explicit Channel Request (User-Specified)

User said: “Create a push notification when order ships” 
Trigger
  ↓
Push
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”
SeverityHIGH
Criticalfalse
ActionableRequires Action
InteractionUSER TRANSACTION
Trigger
  ↓
In-App
  ↓
Email
  ↓
HTTP Request
  method: POST
  url: "{{payload.webhookUrl}}"
  headers: [{ key: "Content-Type", value: "application/json" }]
  body: [
    { key: "event", value: "payment_failed" },
    { key: "subscriberId", value: "{{subscriber.subscriberId}}" }
  ]
  continueOnFailure: true
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” 
Trigger
  ↓
HTTP Request (stepId: "fetch-plan")
  method: GET
  url: "https://api.example.com/users/{{payload.userId}}/plan"
  responseBodySchema: {
    type: "object",
    properties: {
      planName: { type: "string" },
      renewalDate: { type: "string" }
    },
    required: ["planName", "renewalDate"]
  }
  ↓
Email
  subject: "Your {{ steps.fetch-plan.planName }} plan"
  body: "Your plan renews on {{ steps.fetch-plan.renewalDate }}."
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