User guide · Automation & AI
Workflows
Multi-step automations started by messages, contacts, campaigns or your own systems.
On this page
Workflows run a series of steps automatically: ask questions, wait for answers, tag the contact, hand over to a team, call your own systems. Build them in EngageWorkflows.
Triggers
Each workflow starts from one trigger:
| Group | Triggers |
|---|---|
| Messages | Keyword in message, any inbound message, new conversation |
| Inbox | Conversation assigned |
| Contacts | Tag added, contact created, contact updated, contact field changed, contact enters or leaves a segment |
| Campaigns | Reply after campaign, campaign started or completed, campaign message delivered, read or failed |
| Forms and integrations | WhatsApp Flow submitted, inbound webhook received |
Steps
| Group | Steps |
|---|---|
| Messaging | Send text, template, media, reply buttons, list message, WhatsApp Flow or location |
| Flow control | Wait for reply, delay, branch on reply |
| CRM actions | Add tag, update contact, assign team |
| AI | AI reply from the knowledge base, AI collect field |
| Integrations | HTTP request to your own system, branch on its response |
Use contact details and earlier answers inside messages, for example the contact’s name or the last reply.
Publish and monitor
- Build the workflow as a Draft and test it on your own number.
- Publish it. Published workflows are view-only; duplicate one to make changes safely.
- Open its runs to see each conversation’s current step, status and any failed step.
Note
A workflow pauses for a conversation as soon as an agent replies there, so customers never get an automatic answer in the middle of a human one.
WhatsApp Flows
The WhatsApp Flows tab lists Meta’s native forms: multi-screen forms that open inside WhatsApp, for bookings, sign-ups or surveys. Send one from a workflow, a campaign or the inbox; the answers are saved on the contact.
Still stuck? Contact us with what you were doing and the exact message you saw.