Automations and chat flows

14 triggers, 18 actions, and no-code chat journeys.

Automations react to what happens in your WhatsApp account — a message arriving, a tag being added, an order placed, an invoice going overdue — and run a sequence of actions. Chat flows are the visual counterpart: multi-step conversations built from nine node types, with no code.

Lead QualifierNew MessageTestSave & enable
Trigger
New message received
From a new contact
Condition
Message contains
"price" or "rate"
Action
Send template
wacrm_price_list
Action
Assign to
Priya · Sales
Else
Add tag
Needs follow-up
5 of 9 node types

How it works

  1. 1

    Pick a trigger

    Fourteen of them: new or first message, keyword match, new contact, conversation assigned, tag added, a schedule, order placed, invoice paid or overdue, appointment booked or confirmed, a reply to a broadcast, or a deal moving stage.

  2. 2

    Chain the actions

    Eighteen: send a message, template, reply buttons, list menu or product; add or remove tags; assign an agent; update a contact; create a deal, invoice or appointment; notify a teammate; call a webhook; wait; branch on a condition; close the conversation; or run the AI chatbot.

  3. 3

    Or draw the conversation

    Flows use nine node types — start, send message, buttons, list, collect input, condition, set tag, handoff, end — validated before publishing so a customer never hits a dead end.

The specifics

  • Ready-made templates to start from: welcome message, out of office, lead qualifier, AI chatbot.
  • Run logs for every automation: what fired, what it did, and why it skipped.
  • Loop protection is built in, so a tag-triggered automation that adds tags cannot run away.
  • Variable interpolation puts the contact, order, invoice, appointment or deal into the message text.
  • Time-based and event-queued automations run on a sweep, so they fire within a few minutes of being due rather than to the second.

Questions people ask

What can trigger an automation?
Fourteen events: new message received, first inbound message, keyword match, new contact created, conversation assigned, tag added, a time schedule, order placed, invoice paid, invoice overdue, appointment booked, appointment confirmed, a reply to a broadcast, and a deal changing stage.
What is the difference between an automation and a flow?
An automation reacts to an event and runs actions in the background. A flow is a conversation: it asks the customer something, waits for the answer, and branches on it.
Do I need to write code?
No. Both are built in the interface. There is a REST API and webhooks if you want to go further.

Related

All features · Compare with other platforms