Workflows

Workflows automate journeys in real‑time, perfect for lifecycle messaging, operational alerts, or any multi‑step logic that should run the moment a user does something.

Workflows connect to the tools you already use—e‑mail provider, Slack, WhatsApp, internal APIs—so you keep channel flexibility and existing templates.

---

1. Workflows Home

UI Zone	What you can do
Tabs – Published · Draft · Archived	Switch between live, draft‑mode, or shelved flows.
Workflow Cards	Toggle Running/Paused, see counts for Triggers & Steps, click to open the canvas.
Create Workflow	Opens a blank canvas.
Upcoming Published Schedules	Shows the next scheduled triggers (great for weekly newsletters).
Notification Settings	Choose a team e‑mail group to receive run summaries; manage members via side‑panel.

---

2. Workflow Canvas Editor

The canvas is a drag‑and‑drop builder where you chain Triggers ➜ Steps ➜ Actions to form your journey.

Core building blocks

Block	Purpose	Key options
Trigger	Defines when a user enters the workflow.	Scheduled, Profile Property, User Event, API.
Step	A point in the flow that can hold one or more Actions.	Delay before entry, additional audience filters.
Action	The thing that actually happens.	Send e‑mail/Slack/etc., call HTTP webhook, update profile, branch A/B.
A/B Split	Route users into two or more variants for experimentation.	Control % split, compare downstream results.
Entry Criteria	Top‑level gate applied before any trigger fires.	Entry limit, re‑join delay, “must‑have‑performed event in last X”.
Exit Criteria	Rules that eject a user mid‑flow.	Event performed, profile/segment condition.

---

3. Example Recipes

Scenario	Flow outline
User Onboarding Series	Trigger: signup event → Step 1 send welcome e‑mail → Wait 4 h → Step 2 send verify‑email reminder → Wait 2 days → Step 3 send final reminder.
Abandoned Cart	Trigger: checkout_started event → Delay 2 h → Step 1 e‑mail “Finish your purchase” (filter has_not purchase_completed). Exit criteria: user performs purchase_completed.
Weekly Newsletter	Trigger: Scheduled (Fri 09 am) → Step 1 send newsletter via e‑mail → Step 2 Track Email Sent event for user.
A/B Subject Line Test	Same newsletter flow, but first step is an A/B Split (50/50) with two e‑mail actions, each using a different subject line. Compare open/click rates downstream.

---

4. Connecting Channels

Actions surface your integrations list; simply choose:

• E‑mail – any provider you’ve connected (SendGrid, Postmark, etc.)

• Chat – Slack, WhatsApp Business, Discord, etc.

• Webhook – raw HTTP POST/PUT/PATCH/GET to hit internal APIs (add headers, JSON body, read response).

Each action can include Liquid‑style placeholders for profile, event, or computed data ( {{ user.properties.firstName }} , {{ triggerEvent.properties.orderTotal }} ).

---

5. Best Practices

1. One objective per workflow – onboarding, re‑engagement, upgrade—keep them focused.

2. Guard with Exit Criteria – prevents over‑emailing once a user converts.

3. Use Segments & Computed Props – cleaner filters, easier maintenance.

4. Start simple, iterate – ship a minimum viable flow, then add branches/A‑B after results.

5. Monitor upcoming schedules – turn on e‑mail notifications so the team knows when big blasts fire.