Skip to content

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.

What Automations are

RouteWhat you do
/automation and /whatsapp-app/automation-listList bots: search, enable/disable, copy, delete, create (name + channel + WA number or RCS bot)
/whatsapp-app/automation-builderVisual flow builder (full-screen editor)
/whatsapp-app/automation-analyticsUsage / charts per workflow
ToolWhat it is
WorkflowworkflowName, graph nodes / edges, fallbackMsg, channel (whatsapp or rcs)
BindingWhatsApp: wabaId + mobileNumber (+ phoneNumberId). RCS: botId
KeywordsUnique keywords per channel/number so two bots do not clash
PublishStatus InDraft or Publish; isActive on/off
API nodeOutbound HTTP from the flow (GET / POST / PATCH / PUT / DELETE, url, headers, params, body)
Catalog stepgetCatalogProducts / catalogId (WhatsApp Commerce)
Inbox handoffTeam 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

AutomationsWhatsApp Flows
Whose productThis portalMeta
What the user seesChat messages, keywords, buttons you scriptNative multi-screen form
SetupGraph builder + publishflow_json + publish on the WABA
Typical triggerInbound message or keywordTemplate Flow button or send flowId
ChannelsWhatsApp and RCSWhatsApp only
MenuAutomation list / builderWhatsApp 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

  1. Connect a WhatsApp number and/or an RCS bot.
  2. Keep wallet credits for outbound bot replies.
  3. Optional: a Commerce catalog if the flow sells products (catalogId).
  4. Optional: Team Inbox agents for live handoff.
  5. Optional: My CDP so intake can carry workflowId / workflowName / stepKey.

Create and bind

  1. Open Automation list → create.
  2. Set workflowName and channel (whatsapp or rcs).
  3. Bind the channel:
    • WhatsApp: wabaId + mobileNumber (and phoneNumberId when the number has one).
    • RCS: botId.
  4. Save. The workflow starts as InDraft (isActive off 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) with url, 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:

  1. Set status to Publish.
  2. Turn isActive on.
  3. Send the keyword from a test handset to the bound number / bot.
  4. 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 botId as 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

SituationWhat it means
Keyword already usedAnother bot on this number / botId owns that keyword
Status InDraftPublish and set isActive before testing inbound
Wrong channel bindingWhatsApp needs wabaId + mobileNumber; RCS needs botId
No replies sentWallet credits, or the node never reached a send step
Assign to bot does nothingworkflowId must match a published workflow on this channel
Catalog step emptyConnect 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.

Was this page helpful?