Connect a node to WhatsApp Business so it can receive and reply to messages on a dedicated number.
Status: beta. Setup is manual right now — contact support for provisioning. A self-serve flow is coming in 2026 Q3.
What you get
- A dedicated WhatsApp Business number owned by your workspace.
- All inbound messages route to the connected node’s chat pipeline.
- Outbound replies sent by the node appear as WhatsApp messages.
- Attachments (images, PDFs, audio) are staged into the workspace’s artifact shelf.
Typical use cases
- Customer intake — a support node that answers questions and escalates to a human when it hits a decision gate.
- Appointment booking — a scheduling node that looks at calendar availability and confirms via WhatsApp.
- Field-team updates — a project-manager node that receives field reports by WhatsApp and summarizes them into the workspace timeline.
Setup (manual, beta)
- Workspace → Settings → Channels → Add WhatsApp.
- Contact support — they’ll provision a number and issue a Business API token.
- Paste the token into the form.
- Assign the channel to a node.
Full self-serve onboarding (including number purchase flow) is on the roadmap.
Message model
Inbound WhatsApp messages are treated as chat messages to the assigned node. The same skill-lookup + instruction-following pipeline runs — so a WhatsApp message saying “Find leads in the SMB retail segment” triggers find-leads exactly like a web-UI chat would.
Replies go back as WhatsApp messages, respecting the platform’s text-length limits.
Limitations today (beta)
- Manual provisioning (support-driven).
- No group chat support — one-to-one conversations only.
- No quick-reply button templates yet.
- Voice messages not transcribed.
Last updated on