Flows
Flows — User Guide
Who is this for? Anyone who builds automations in the CRM — no coding needed. What you'll learn: how to build flows from a one‑step reminder to a full multi‑branch journey, what every piece does, and where the limits are. (Confluence note: diagrams are Mermaid; the rest is plain text and tables.)
1. What are Flows?
A Flow is an automation you build by connecting boxes on a canvas. It works like a recipe:
When something happens → if some condition is true → do these things.
Examples you can build:
When an order is approved → send a thank‑you SMS.
When a call is completed → if it was a sale → add a tag and create a follow‑up task.
Every day at 9am → check a list and send a reminder.
When a lead comes in from a specific funnel → wait 1 day → send an email, then an SMS.
Why use Flows?
Save time — the CRM does repetitive work for you.
Be consistent — every customer gets the same great treatment.
React instantly — messages and tasks happen the moment something occurs.
No developer required — you build it visually.
2. The three building blocks (core concepts)
Every flow is made of three kinds of steps:
Block | What it is | Examples |
|---|---|---|
🟢 Trigger | The one event that starts the flow. Every flow has exactly one. | "When an order is approved", "On a schedule", "When a webhook is received" |
🔵 Control | Decisions and structure — they shape the path. | If / Else, Switch, For each, Wait, Stop if, End |
⚙️ Action | The actual work — a side effect. | Send SMS, Send Email, Add tag, Create task, HTTP request |
A flow reads top‑to‑bottom along the connections you draw between steps.
truefalse
🟢 When order approved
🔵 If order total > 100?
⚙️ Send SMS
⚙️ Send Email
End
3. The builder, at a glance
The builder has three areas:
Palette (left): the catalog of steps you can add — Triggers, Control, Actions.
Canvas (middle): where you place steps and connect them.
Inspector (right): where you configure the selected step. It also has a Runs tab to watch executions.
Top bar: the flow name, an Active switch, and Save. A yellow "unsaved" chip reminds you to save.
4. Build your first flow (step by step)
Let's build: When an order is approved, send a thank‑you SMS.
Open Flows → Create flow. Give it a name (e.g. "Order thank‑you SMS").
From the palette, click When event happens. In the inspector, pick the event order‑approved.
Click Send SMS in the palette. A second box appears.
Connect them: drag from the dot at the bottom of the trigger onto the Send SMS box. A line appears.
Select Send SMS. In Message, type your text. Use Custom values to insert the customer's name (see §7).
Click Save.
Flip the Active switch on. Done — it now runs automatically.
💡 Steps are connected by dragging from the dot at the bottom of one step onto another. To remove a connection, click the small × on the line.
5. Triggers — how a flow starts
A flow has exactly one trigger (the green entry step). There are three families:
Event triggers ("When event happens")
Pick an event from the dropdown:
Event | Fires when… |
|---|---|
| an order changes to that state |
| an order is refunded |
| a chargeback or void happens |
| someone is added manually in the CRM |
| a lead comes in from an integration/funnel |
| an opportunity's stage changes |
| an opportunity is assigned to an agent |
| a call finishes (with its recording) |
| a task is completed / due today |
| subscription lifecycle |
Integration type filter: for
contact-createdyou can pick an Integration type (e.g. ClickFunnels). If set, the flow runs only for leads from that integration. Leave it blank to run for all.
On a schedule (cron)
Runs on a timetable. You don't write cron — a friendly builder lets you pick Every few minutes / Hourly / Daily / Weekly / Monthly and the time/day. (See §10.)
On webhook received
Runs when an external system posts to your flow's unique URL. You choose a slug; the incoming data is available as webhook.* values.
6. Conditions — making decisions
Conditions live inside If / Else, Switch, and Stop if. A condition is three parts:
Field · Operator · Value — e.g. Order total · greater than · 100.
Field: pick from a friendly dropdown grouped by entity (e.g. Order › Total, Customer › Email). The available fields depend on your trigger (an order flow shows order fields, a call flow shows call fields, etc.).
Operator: adapts to the field type — text gets contains / equals / starts with, numbers get greater / less than, dates get before / after / on date, yes/no gets is true/false.
Value: the editor adapts too (a date picker for dates, a true/false selector for yes/no, etc.). Some operators (exists / not exists) need no value.
Match all / any: combine several rules with All (every rule must be true) or Any (at least one). You can nest groups for advanced logic.
7. Custom values (shortcodes) — personalize messages
Anywhere you write a message (SMS body, Email body/subject, HTTP body), click Custom values to insert a placeholder like {{contact.first_name}}. At send time it's replaced with the real value.
You can pull:
Contact info: name, email, phone, etc.
Order info, and last order products (e.g. the names of what they bought).
For the trigger's subject and related records.
Lists (like several product names) are inserted comma‑separated automatically (e.g. "Widget A, Widget B").
8. Actions — the things a flow does
Action | What it does | Good to know |
|---|---|---|
Send SMS | Texts the contact. | Insert Custom values; optionally attach a vCard from a dropdown; Send test to your phone first. |
Send Email | Emails the contact (raw HTML). | HTML editor + live Preview, CC/BCC as chips, Send test. Your HTML is sent as‑is. |
Add tag / Remove tag | Tags the contact. | Type each tag and press Enter (chips). |
Create task | Creates a follow‑up task. | Pick a Task type from the list, due‑in days, notes. Needs an opportunity to attach to — otherwise it's skipped (see limits). |
Update opportunity | Sets status / substatus. | Both are dropdowns; substatus options depend on the chosen status. |
Update contact field | Writes one contact field. | Pick the field from a safe dropdown (e.g. SMS opt‑in), set the value (supports custom values). |
Notify user | In‑app notification to a user/agent. | Title + body; defaults to the assigned agent. |
HTTP request | Calls an external API. | Method, URL, headers (key/value), body template. Test request shows the response status, body and headers. |
Cancel scheduled SMS | Stops a contact's pending SMS sequence. | No settings. |
Test buttons: SMS, Email, and HTTP each have a test button. Tests fill custom values using a sample contact (your most recent one), so you see realistic output before going live.
9. Control structures — shaping the path
Control | Purpose |
|---|---|
If / Else | Two paths: true and false, based on conditions. |
Switch | Many paths (cases) + a default — e.g. route by opportunity substatus. |
For each | Repeat steps once per item in a list (e.g. each product in the order). |
Wait | Pause the flow (minutes/hours/days), optionally respecting quiet hours and skipping weekends, then continue. |
Stop if | End the flow early unless conditions are met (a guard). |
End | Explicitly finish the flow. |
About For each (important)
Pick a list (e.g. Order items) from the dropdown — the loop variable is set up for you. The steps under the loop's "for each" port run once per item, and come back automatically to process the next one. You do not need to draw a line back. Inside the loop you can use the item's fields (e.g. item › Product type). To stop the whole flow from inside a loop, use an End step.
About Wait
A Wait pauses the run and resumes later — even days later. The flow remembers exactly where it was. Use it for drip sequences ("wait 2 days, then email").
10. Scheduling (the "On a schedule" trigger)
No cron syntax needed. Choose a Repeat:
Every few minutes (5/10/15/30)
Hourly (pick the minute)
Daily (pick the time)
Weekly (pick days + time)
Monthly (pick day of month + time)
A plain‑English summary shows what you chose ("Every day at 09:00"). An Advanced toggle lets power users type a raw cron expression.
11. Connecting, saving, and turning a flow on
Connect: drag from a step's bottom dot onto the next step. Branching steps (If/Else, Switch, For each) have labeled ports (true/false, case names, "for each"/"after").
Save: click Save. A flow can be saved as a draft.
Validate & activate: flip Active. The system checks the flow first. If something's off, a panel lists the issues — click an issue to jump to the step that needs attention. Common checks: exactly one trigger, required fields filled, every connection points somewhere, no unreachable steps.
Pause: flip Active off (you'll be asked to confirm).
12. Watching executions (the Runs tab)
Open a flow and switch the right panel to Runs to see what actually happened.
Each run shows a status: completed (green), failed (red), waiting (amber — paused at a Wait), running (blue), or pending.
Expand a run to see every step with its own status:
ok — ran successfully.
branched — a decision was made (shows which way).
skipped — the step couldn't run (e.g. no contact, no opportunity) — and it shows why. The flow keeps going.
paused — waiting (shows the resume time).
failed — an error (shows the message).
Click a step to highlight it on the canvas.
The list auto‑refreshes while a run is active, and there's a manual refresh button.
🔍 This is your main tool to confirm "is my flow working?". A skipped step is normal (a condition wasn't met / no data); a failed step means an error you should look at.
13. Recipes — from simple to elaborate
Recipe A — One‑step thank‑you (beginner)
order-approved → Send SMS "Thanks {{contact.first_name}}!"
Recipe B — Branch by value (intermediate)
order-approved → If Order total > 100 → true: Send SMS + Add tag "vip" · false: Send Email.
Recipe C — Drip sequence with a wait (intermediate)
contact-created (Integration type = ClickFunnels) → Send Email (welcome) → Wait 2 days → Send SMS (check‑in).
Recipe D — Per‑item processing (advanced)
order-approved → For each Order items → If item › Product type = digital → Add tag "digital‑buyer". (Loops automatically; continues after.)
Recipe E — Pipeline routing (advanced)
opportunity-substatus-changed → Switch on substatus → case "no‑answer": Create task "follow‑up" · case "sale": Add tag "won" + Notify user · default: nothing.
Recipe F — External sync (advanced)
order-approved → HTTP request POST to your API with a JSON body using custom values → If http.ok is true → Add tag "synced" · else Notify user "sync failed".
14. Best practices
Test before activating. Use Send test (SMS/Email) and Test request (HTTP).
Use conditions to stay relevant. E.g. only SMS contacts who opted in.
Respect quiet hours. Use Wait's "respect silence period" / "avoid weekends" for messages.
Watch the Runs tab after going live to confirm the first few executions.
Name flows clearly (what + when), so the list stays readable.
Start simple, then add branches. Build the happy path first, then handle the edge cases.
15. Limits & things to know
One trigger per flow. To react to two different events, build two flows.
contact-createdvscontact-created-manualare different: integration leads vs manual CRM entries.Create task needs an opportunity. If there's no opportunity to attach the task to, the step is skipped (it won't stop the flow). Use it in opportunity/order flows.
Calls:
call-completedfires once a call has its recording (outbound) / conference + recording (inbound). The "customer" is resolved correctly whether the call was inbound or outbound.Email is sent as raw HTML you design — there's no drag‑and‑drop template builder (yet). The Preview shows the design; shortcodes are filled only when you send a real/test email.
Runs history shows the most recent 50 executions per flow.
Tags as triggers aren't available yet (you tag with actions, not trigger on tags).
Feature availability depends on your account having Flows enabled.
16. Quick glossary
Term | Plain meaning |
|---|---|
Trigger | What starts the flow. |
Condition | A yes/no check (field + operator + value). |
Action | Something the flow does (send, tag, task…). |
Branch | A path out of a decision (true/false, a case, the loop body). |
Custom value / shortcode | A placeholder like |
Run | One execution of the flow. |
Skipped | A step that didn't run because its prerequisite wasn't met (normal). |
Wait | A pause that resumes later. |
vCard | A contact card you can attach to an SMS. |
Webhook | A URL external systems can call to start a flow. |
Need a new trigger, action, or field that isn't here? Ask the product/engineering team — the system is built to add them quickly, and they appear in the builder automatically.