Skip to content

Workflows & automation

Workflows do work for you automatically. For example: when someone sends “price”, reply with the price list and tag them as a lead.

This page shows how to build them. For every trigger, condition, action and variable, and exactly how they behave, see the Workflow reference.

Go to Automation → Workflows in the sidebar.

A workflow has two levels:

  • Workflow (master): the container, with a name, a description and a type.
  • Steps: the rules inside it, listed on the left of the editor. Each step is trigger → conditions → actions. Use Add step to add another, for example a follow-up that waits for a button tap. A workflow can have up to 10 steps. Click the fold icon at the top of the steps panel to shrink it to step numbers and get more room.
Part Question it answers Examples
Trigger When does this run? Incoming message, webhook, manual start, message status
Conditions Only if… Message includes “price”, contact is in a group, a tag is set
Actions Then do… Send a template, tag the contact, post to a webhook, hand off to an AI bot
  1. Click Add Workflow.

  2. Enter a Workflow name, e.g. Welcome new customers. To add a description, click Add a description (optional).

  3. Choose How should it run?

    • Automatic: runs by itself whenever its trigger happens.
    • Manual: runs only when you start it for selected contacts or groups.
  4. Choose Start from (automatic workflows only). Pick Blank, or a starter that creates the steps for you:

    • Reply to a keyword: replies when a message contains “price”.
    • Reply to every message: sends a template to anyone who messages you.
    • Follow up after a button tap: sends a template with buttons, then replies when the customer taps “Yes”.
    • Tag interested contacts: adds a tag when a message contains “interested”.
    • Send messages to your CRM: posts each incoming message to your webhook URL.
    • Hand off to an AI bot: lets your AI bot answer when someone asks for help.

    The form tells you what is left to fill in, such as which template to send or the keyword to match.

  5. Choose Build with:

    • Form editor: fill in step-by-step sections.
    • Flowchart editor: drag blocks onto a canvas and connect them.

    You can switch editor at any time; both edit the same workflow.

  6. Set up the trigger. Click Choose a trigger, search or pick from the list, e.g. Customer sends a message.

    For messages, fill in the sentence under When does it run?: When a customer sends a WhatsApp Text message that contains price. Choose the channel and message type, then optionally the text to match (contains, is exactly, starts with or is not). For button replies, match the button title. Leave the text empty to run on every message of that type. Matching is case-sensitive. The green line below the sentence shows what will run.

  7. Need more rules? Open Advanced → Conditions and click Add a condition group. Pick what to check (tags, groups, variables, the Channel the message came in on, and more) and how, such as is, contains or starts with. Channel lists your WhatsApp numbers, Instagram accounts and Facebook Pages: choose one or several with is one of or is not any of, for example to answer only on your support number. Join rules with AND (all must be true) or OR (any one is enough); groups are joined the same way. Closed groups show a readable summary, and Advanced → Variables lists the values you can insert into messages.

  8. Click Next: Actions under the trigger (or Actions in the section list) and add one or more actions. Click Choose an action and search, e.g. “template” or “tag”. The most used actions are listed under Popular. For messages, choose who to Send to (the customer, or another number) and how long to Wait before sending, then click Write message.

  9. Click Save (or press Ctrl+S). You stay in the editor, and a message confirms the save. Then turn the workflow on from the Set up panel or with the switch on its card.

A Set up panel at the top of the editor, in both the form and the flowchart, lists what still needs attention. It starts as one line showing how many items there are; click it to open the list. Each row names the step and where to fix it (Trigger, Conditions or Actions). Click a row to jump there.

  • Needs setup: anything a step needs before it can run, such as a template to send, the message text, groups or tags, an AI bot, or the channel.
  • Worth checking: things that will not stop the workflow but may not do what you expect: two steps that start on the same message (both would reply), a step waiting for a step that was deleted, template variables with no value, and steps switched off inside a workflow that is on. You can still click Turn on anyway.

When nothing is left and the workflow is off, click Turn on workflow. It saves your changes first. Save asks before saving when there are things to check: click Save anyway or Keep editing. It asks once for the same set of warnings.

While you have changes that aren’t saved, an Unsaved changes tag shows next to the name. Closing the editor (the Close button, Esc or ✕) then asks whether to Save and continue, Discard changes or Keep editing.

To change a workflow later, open its card menu (⋯) and choose Edit in form or Edit in flowchart. The Edit button on the card opens the editor you used last.

The flowchart editor shows each rule as blocks on a canvas:

  • A green When block is a trigger. It starts a step and shows its platform, message type and conditions.
  • Purple Do blocks below it are its actions. They run from top to bottom.
  • A dashed line labelled next step connects a step to the trigger of another step.
  1. Drag a Trigger from the left panel onto the canvas, or click it.
  2. Click the block to open its settings. Choose the trigger, platform and message type, then add conditions and variables.
  3. Click + under the block and pick an action. Click the new action block to configure it, for example to choose a template.
  4. Keep adding actions with +. To insert an action between two others, use + on the upper one.
  5. To wait for the customer’s reply, click + under the last action and choose New step. Give the new trigger the reply it should wait for, e.g. Interactive quick reply buttons with a button title condition.
  6. Click Save. Blocks that still need settings are outlined in red with a short message.

Other things you can do on the canvas:

  • Drag from the bottom handle of a block into empty space to create the next block there.
  • Drag between handles to connect blocks.
  • Select a block or a line and press Delete to remove it. Deleting a trigger also removes its actions.
  • Click Auto layout to tidy the blocks.
  • Press Ctrl+Z (Cmd+Z on Mac) to undo a change and Ctrl+Shift+Z to redo it, or use the arrow buttons in the header. Undo goes back to the last save. Ctrl+S saves.
  • Close in a block’s panel only closes the panel; your changes stay on the canvas until you click Save in the top bar.
  • To copy blocks, select them (Shift-drag a box, or Ctrl-click each one) and press Ctrl+C, then Ctrl+V to paste. A pasted step is a new step named “… (copy)”, with its actions and the links between the copied blocks. You can also paste into another workflow.
  • Each saved trigger block shows how many contacts finished it and how many actions failed. A block marked Often fails needs a look: select it and click the history icon to see recent runs and the reasons.

The main ones are below. See the Workflow reference for every option and its settings.

Trigger Runs when…
Customer sends a message A customer sends a message. Narrow it by message type: text, image, button reply, flow response, order, payment and more
Webhook is called Another system sends a POST with a JSON body to the workflow’s unique URL. The URL appears in the trigger settings after you first save the workflow
Started manually You start it from Contacts (Trigger Workflow) or from another workflow
Message is delivered or read A message you sent is sent, delivered or read
Webhook action replies A Send to a webhook action gets a response
Pipeline stage changed A card moves to another stage in a pipeline. Shown when Pipelines is on for your account
No reply for a while A conversation goes quiet: the customer doesn’t answer you, or nobody answers them. See Time-based triggers
Follow-up is due A follow-up task reaches its due time, or is still open some time after it
Integration triggers E.g. new order in Shopify or abandoned cart. These depend on your connected integrations

These start from the clock rather than from an event, and run for one contact at a time.

No reply for a while watches one side of a conversation:

  • The customer hasn’t replied: after a message of yours, such as a quote or a reminder, the customer stays silent for the time you set. Good for a gentle nudge.
  • Nobody has replied to the customer: a customer’s message sits unanswered by your team or a bot. Good for reassigning the chat or alerting someone.

Set how long to wait, from 5 minutes to 30 days. Each new message restarts the wait. It runs once per silence: after it has run for a contact, it won’t run again until the other side writes. That means a nudge sent by the workflow itself can’t set it off a second time. Messages and conditions can use {{waiting_hours}} and {{waiting_since}}.

Follow-up is due runs for the follow-up’s contact, once per follow-up, including follow-ups created by workflows. Choose when it falls due, or when it’s still open some time after its due time; in that case nothing happens if the follow-up was completed in time. Messages and conditions can use {{followup_text}}, {{followup_due_at}}, {{followup_assignee}} and {{followup_overdue_hours}}.

The main ones are below. See the Workflow reference for every option and its settings.

Action What it does
Send a template Send an approved template to the customer or another number, optionally after a delay
Send a message Send text, media, buttons, a list, catalog, flow or payment request (within the 24-hour window)
Send to a webhook Send data to another system’s URL (REST or GraphQL)
Add to groups or tags Organise the contact
Mark as lead Flag the contact as a lead, so it counts in lead reports
Assign to team member Give the chat to a teammate. See Assign chats to your team
Create follow-up Add a follow-up task for a teammate. See Create follow-ups
Hand off to an AI bot Hand the chat to an AI bot, with an idle time, exit message and buttons
Run code Run custom JavaScript
Save data Save details to Orders or Contacts
Update a state value Set a state value the workflow can read later
Repeat a step / Start another workflow Run a step again, or start another workflow
Move deal to stage / Create deal Move the contact’s card to a stage, or add a new card to a pipeline
Mark deal won or lost Move the contact’s card to the pipeline’s first won or lost stage
Change deal owner Give the card to a teammate, or to whoever the chat is assigned to
Update deal value Set the card’s value to a number or a variable, e.g. {{order_total}}

The deal actions are in the Pipelines group and need Pipelines turned on for your account. Mark deal won or lost, Change deal owner and Update deal value change the card that started the workflow (with the Pipeline stage changed trigger). Otherwise they change the contact’s most recently updated open card in the chosen pipeline. If the contact has no open card there, nothing happens and the run says why.

Assign to team member sets who the chat is assigned to, as if you had assigned it in the inbox. Choose how:

  • A specific teammate: always the same person.
  • Round-robin: the teammates you choose take turns.
  • Least busy: the chosen teammate with the fewest chats waiting for a reply. Ties go to whoever is next in turn.
  • Unassign: remove the current assignee.

Turn on Only if the chat isn’t assigned yet to leave chats that already have someone. It’s on by default for round-robin and least busy. The teammate gets a notification in the app and on their phone. Teammates who have left the team are skipped.

Giving the chat to a teammate turns its AI switch off, so your AI bot stops replying. Turn on Keep AI bot replies on if the bot should keep answering.

Create follow-up adds a task to the Follow-ups page. Write what needs doing (variables like {{senderName}} work), choose when it’s due, and who it’s for:

  • The chat’s assignee: the account owner if the chat isn’t assigned.
  • A specific teammate
  • Nobody: anyone on the team can pick it up.

Leave Link it to the contact’s open pipeline card on to show the follow-up on that card too.

The main ones are below. See the Workflow reference for every option and its settings.

Use variables such as {{senderName}}, {{messageText}} and {{senderID}} in messages and conditions. Data from flows, webhooks and integrations becomes available automatically as variables.

To add your own, open Advanced → Variables and click Add variable. Give it a name (letters, numbers and _), then choose where its value comes from:

Use the copy button to copy {{name}} for pasting into a message. The State variables tab lists values kept per contact across steps; manage those from States in the workflow card menu.

  1. Trigger: Customer sends a message → Flow (your “Get a quote” WhatsApp Flow, with a budget question; when you add its options, give Above ₹50,000 the value above_50000).
  2. Condition: {{budget}} is above_50000 (conditions see the option’s value, not its label).
  3. Actions:
    • Send a message: “Thanks {{senderName}}! A specialist will contact you shortly.”
    • Add to groups or tags: tag Qualified Lead
    • Send to a webhook: send the lead to your CRM
    • Hand off to an AI bot: your sales bot

Conditions compare text with is, is not, contains and starts with, and numbers with is greater than and is less than. To sort leads by budget, either ask for a number and use is greater than, or give the form question fixed options (ranges) and check which option was picked.

Before turning a workflow on, send a step to your own WhatsApp to check it. Open the step and click Send a test. In the flowchart, select a trigger block and click the send icon. Enter your number with the country code, fill in sample values for any variables, and click Send test.

The step’s messages and templates go to you straight away, without their delays. Other actions, such as tags, webhooks, assigning a teammate, follow-ups or deal changes, are listed but not run, so nothing in your account changes. Tests don’t count in activity and don’t start the next step. Unsaved changes are included, but the step must have been saved once.

Messages that aren’t templates only arrive if your number has messaged the business number in the last 24 hours. Templates always arrive.

Each time you save a workflow, a version is kept. The latest 30 are kept. To go back, open the workflow and click History in the header. Versions are listed newest first, with who saved them and how many steps and actions they had. Click a version to see its steps and what restoring it would change: steps that come back, steps that are removed and steps that change.

Click Restore this version and confirm. The steps are replaced with that version, and the editor reloads them. Whether the workflow is on or off doesn’t change. Before restoring, the current version is kept in history, so you can undo a restore by restoring that one. Unsaved changes in the editor are lost when you restore.

If a restored version brings back a deleted step that starts from a webhook, that step gets a new webhook address. Update the address in the app that calls it.

A card marked Needs setup (2) has steps that still need settings, and Empty means no step has a trigger or an action yet. Turning one of those on asks first; click Turn on anyway only if you know why.

Each workflow card, and the list view, shows the last 7 days: how many contacts finished a step, how many actions were sent, and how many failed. Hover over it for all-time totals, the success rate and when it last ran. In the editor, each step in the steps panel shows its own finished and failed counts. The numbers are kept up to date as the workflow runs.

To see who a step ran for, open the workflow, select the step and click Runs. Each row shows the contact, the action, the result and when it happened, newest first. Failed rows show the reason, for example a template with unfilled variables. Use the Failed filter to find problems quickly, and Load older runs to go further back.

  • Library: ready-made workflows. Open the Library tab and search, or filter by category (Sales, Support, Marketing, E-commerce, Lead capture). Popular shows the most used first. Each card lists what you will choose when you use it. Templates for an integration, such as Shopify, appear once that integration is connected under Settings → Integrations. Pick one and click Use template. Name your copy and click Create workflow. It opens in the editor and stays off. A Set up list at the top shows what to choose for your account, such as the template to send, the groups, the AI bot, the teammates or the pipeline. Click each item to go to it. When nothing is left, click Turn on workflow.
  • Export a workflow from its card menu, and Import .wabot files to copy workflows between accounts.
Problem Check
The workflow doesn’t run Both switches are on. The channel and message type in the trigger sentence match the message
A variable is empty The variable name and data path in Advanced → Variables
The webhook action fails The URL, method and headers, and that the JSON body is valid
A template isn’t sent The template is approved, and all its variables have values
A “next step” never runs The earlier step finished successfully for that contact, and the reply matches the next trigger’s message type and conditions
A workflow from the Library does nothing Open it and finish the Set up list, then turn it on
A chat wasn’t assigned The chat already had an assignee and Only if the chat isn’t assigned yet is on, or the chosen teammates have left the team. Runs shows the reason
A “No reply” step didn’t run The other side replied before the wait ended, a newer message restarted the wait, or it already ran during this silence. It runs again once the other side writes
A deal action did nothing The contact has no open card in that pipeline, or the pipeline has no won or lost stage. Runs shows the reason
A customer says they got nothing Open the step and click Runs, then filter by Failed to see the reason
Save is blocked in the flowchart Every red-outlined block needs a trigger or an action type, and every action must be connected under a trigger