Flows (Automations) Pro add-on
Flows are workspace automations: “when this happens, do that.” Pick a trigger — an invoice is paid, a payment comes in, a quote is approved, a product is added, an inbox message arrives, an appointment is booked, or a schedule — and an action — send an email, a WhatsApp, an in-app notification, an agent message, or fire an Email Marketing campaign. You build them by chatting with the assistant, no builder to learn, and they run on the platform's automation engine scoped to your workspace only. This page explains the triggers, the actions, how to create one, and how runs are metered.
Where: enable Flows from the App Launcher (Pro add-on); it appears in your navigation as Automations at /automations. Build flows in the visual builder there, or just describe one to the assistant.
Triggers — when a flow fires
A flow starts from one of these:
| Trigger | Fires when… |
|---|---|
| Invoice paid | an invoice is settled. |
| Payment received | money comes in. |
| Quote approved | a customer accepts a quote. |
| Product added | a new product is created. |
| Inbox message | a message arrives in the Inbox. |
| Appointment booked | someone books an appointment. |
| Schedule (cron) | on a recurring time schedule you set. |
Under the hood a flow can be reached four ways — a business event (the triggers above), a schedule, an inbound webhook, or a manual run — but the ones you'll build from chat are the events and schedules.
Actions — what a flow does
Messaging actions reach out to someone:
| Action | What it does |
|---|---|
| Send email | Email someone (e.g. a customer or a teammate). |
| Send WhatsApp | Message a WhatsApp contact (needs WhatsApp connected — see Inbox). |
| In-app notification | Post a bell notification to a user. |
| Agent message | Have the assistant post a message. |
| Dispatch an Email Marketing campaign | Kick off an Email Marketing campaign. |
CRM & commerce actions update your data — so a flow can do work, not just notify:
| Action | What it does |
|---|---|
| Add tag | Tag a CRM contact (e.g. tag everyone who books an appointment). |
| Add note | Attach a note to a CRM contact/company. |
| Update contact | Change a field on a CRM contact. |
| Assign owner | Assign a contact/record to a team member. |
| Approve quote | Approve a quote automatically. |
| Update product | Change a field on a product. |
Branch with A/B split. Between the trigger and the action you can drop an A/B Split — it randomly sends each run down path A or B, so you can test two versions (e.g. two email subjects) and compare. Each branch then runs its own action.
How to create a flow
Two ways, whichever suits you:
- Visual builder. Build the flow on a canvas — drop a trigger, connect it to an action (with an optional A/B split in between), and configure each node. This is the primary way to create and edit tenant flows.
- From chat. Or just describe it to the assistant — e.g. “when an invoice is paid, send the customer a thank-you email,” or “every Monday at 9am, send my VIP list a campaign” — and it sets the flow up for you. You can also ask it to list, pause or delete your flows.
Email actions need a connected sender. A flow that sends email uses your connected email (BYOK Resend — see Keys & Connections). If the workspace hasn't connected one, the flow can't send and tells you clearly to connect email first, rather than failing silently.
Scoped & safe. Chat-built flows are workspace-scoped — they only ever see and act on your workspace's data and run under your permissions. They're a deliberately simple, guard-railed subset of the platform's full automation engine.
Metering — what a run costs
Because flows do real work (send mail, message, dispatch campaigns), tenant flow runs are metered against your workspace credit pool: a base cost per run plus the cost of the action it performs (e.g. an email or a campaign dispatch). That keeps automations honest — a flow that fires a thousand times has a visible, bounded cost — and it draws from the shared workspace pool like other metered work.
Good first flows: “thank-you email when an invoice is paid,” “notify me when a big quote is approved,” “post to the team when an appointment is booked,” or a “weekly newsletter” on a schedule. Start with one, watch it run, then add more.