WhatsApp and RCS Automations
Automations are chatbot / keyword workflows for WhatsApp and RCS. A visual builder (graph of nodes and edges) publishes a bot onto a WhatsApp number or RCS bot. Inbound messages hit the flow; the flow can reply, call an HTTP API, use catalog products, or hand off to Team Inbox.
This is not Meta WhatsApp Flows (in-chat forms). Automations are the chatbot graphs in this portal. There is no public apikey CRUD API for workflows — create, bind, publish, and test here.
What Automations are
| Route | What you do |
|---|---|
/automation and /whatsapp-app/automation-list | List bots: search, enable/disable, copy, delete, create (name + channel + WA number or RCS bot) |
/whatsapp-app/automation-builder | Visual flow builder (full-screen editor) |
/whatsapp-app/automation-analytics | Usage / charts per workflow |
| Tool | What it is |
|---|---|
| Workflow | workflowName, graph nodes / edges, fallbackMsg, channel (whatsapp or rcs) |
| Binding | WhatsApp: wabaId + mobileNumber (+ phoneNumberId). RCS: botId |
| Keywords | Unique keywords per channel/number so two bots do not clash |
| Publish | Status InDraft or Publish; isActive on/off |
| API node | Outbound HTTP from the flow (GET / POST / PATCH / PUT / DELETE, url, headers, params, body) |
| Catalog step | getCatalogProducts / catalogId (WhatsApp Commerce) |
| Inbox handoff | Team Inbox Assign to bot uses workflowId |
Channels
- WhatsApp: inbound on the bound number starts the published flow.
- RCS: inbound on the bound bot starts the flow.
- SMS: not a first-class automation channel in this product.
Automations vs WhatsApp Flows
| Automations | WhatsApp Flows | |
|---|---|---|
| Whose product | This portal | Meta |
| What the user sees | Chat messages, keywords, buttons you script | Native multi-screen form |
| Setup | Graph builder + publish | flow_json + publish on the WABA |
| Typical trigger | Inbound message or keyword | Template Flow button or send flowId |
| Channels | WhatsApp and RCS | WhatsApp only |
| Menu | Automation list / builder | WhatsApp Flows |
Use Automations for 24/7 FAQ, routing, API lookups, and inbox handoff. Use WhatsApp Flows when the customer should fill a structured form inside WhatsApp.
Get ready
- Connect a WhatsApp number and/or an RCS bot.
- Keep wallet credits for outbound bot replies.
- Optional: a Commerce catalog if the flow sells products (
catalogId). - Optional: Team Inbox agents for live handoff.
- Optional: My CDP so intake can carry
workflowId/workflowName/stepKey.
Create and bind
- Open Automation list → create.
- Set
workflowNameandchannel(whatsapporrcs). - Bind the channel:
- WhatsApp:
wabaId+mobileNumber(andphoneNumberIdwhen the number has one). - RCS:
botId.
- WhatsApp:
- Save. The workflow starts as InDraft (
isActiveoff until you publish).
One inbound number or RCS bot should not host two published bots that share the same keyword. Keywords are unique per channel/number.
Builder, keywords, publish
Open automation-builder for the graph: nodes and edges, plus fallbackMsg when nothing matches.
Typical node jobs:
- Send a reply (text, buttons, media)
- Wait for a keyword or user reply
- API node — call your server (
GET/POST/PATCH/PUT/DELETE) withurl,headers,params,body - Catalog step —
getCatalogProducts/catalogId - Hand off to Team Inbox
Keywords start the flow from an inbound message. Keep them unique on that WhatsApp number or RCS bot.
When the graph is ready:
- Set status to Publish.
- Turn
isActiveon. - Send the keyword from a test handset to the bound number / bot.
- Confirm the reply, then a path that reaches inbox if you use handoff.
Unpublished (InDraft) workflows do not answer inbound chat.
Inbox handoff
Team Inbox Assign to bot uses workflowId. The same workflow can also route a live user to an agent (open a ticket in the inbox queue) when a node says so.
Handoff only works if:
- The workflow is Publish and
isActive - It is bound to the same WhatsApp number or RCS
botIdas the open chat - An agent exists if a human must pick up
Analytics
Automation analytics shows usage and charts per workflow: how often it started, where people drop, which keywords fire. Use it after publish, not while the graph is still InDraft.
Typical errors
| Situation | What it means |
|---|---|
| Keyword already used | Another bot on this number / botId owns that keyword |
Status InDraft | Publish and set isActive before testing inbound |
| Wrong channel binding | WhatsApp needs wabaId + mobileNumber; RCS needs botId |
| No replies sent | Wallet credits, or the node never reached a send step |
| Assign to bot does nothing | workflowId must match a published workflow on this channel |
| Catalog step empty | Connect a catalog and pass catalogId |
Next: Team Inbox, WhatsApp Flows if you need in-chat forms, My CDP for intake that starts a workflow, RCS / WhatsApp for the channels the bot sits on.