Deterministic where the outcome needs to be repeatable.
Use Logic Flows for controlled steps, explicit recovery branches for known exceptions, and the shared inbox when a person needs to decide.
Waaru combines deterministic Logic Flows, WhatsApp-native message formats, broadcasts, templates, contacts, a shared team inbox, human handoff, and safety controls on Meta's official Cloud API.
In one line
WhatsApp business automation coordinates inbound replies, structured steps, outbound templates, exception handling, and team ownership. Waaru keeps the configured path explicit and sends uncertain conversations to a person.
Automation guide substantively reviewed .
Maintained by the Waaru product team. Read our editorial and product-claim review method.
Platform free. AI features are paid separately.
The problem
Automation becomes useful when every reply changes an explicit state, every exception has a fallback, and every handoff has an owner. Otherwise the channel produces more messages without reducing operational work.
An inbound message, approved campaign, booking event, or connected business event should create one traceable journey. Deduplicate retries and attach the workspace, sender, contact, and relevant business reference before any message is sent.
Use text and media for context, quick replies for a small choice, lists for a longer set, link buttons for a verified destination, and WhatsApp Flows for structured form input. Keep the selected value visible after the customer responds.
An unexpected reply should not disappear. Ask again, take a safe configured branch, stop the journey, or route to a person with the active step and customer context.
The team inbox should preserve the thread, current flow state, structured answers, and the reason the workflow stopped. A person accepts ownership, replies, and resolves the exception in the same customer conversation.
Use approved templates, preserve opt-in evidence, stop workspace-wide marketing on explicit opt-out, respect quality and sender state, apply rate controls, and make retries idempotent. Unsafe or unknown provider state should fail closed.
Connector pages document the source-ready actions, events, setup requirements, and current limits. Production use still depends on external credentials, provider acceptance, and a representative end-to-end test before customer traffic.
It is the use of approved WhatsApp messages, structured workflows, business events, broadcasts, and team ownership to move a customer conversation through a defined operating process.
Yes. Waaru uses Meta's WhatsApp Business Platform Cloud API and the associated sender, template, quality, webhook, and policy model.
Yes. AI agents and MCP access are part of the approved launch release. AI is optional. Deterministic Logic Flows and the human inbox continue to work without a model.
The current executable V2 contract registers 28 deterministic node types, with limits of 200 nodes and 400 edges per flow.
Public signup is open. The platform is free. AI features are paid separately. Meta delivered-template charges remain separate.
The integration directory documents source-ready connector actions, events, setup, and boundaries. Confirm external credentials, provider acceptance, and the exact operation required before production use.
Research notes
Meta documents WhatsApp Business Platform Cloud API architecture and operation.
Meta for Developers · Accessed 8 August 2026
WhatsApp's business messaging policy governs acceptable use and customer control.
WhatsApp Business Messaging Policy · Accessed 8 August 2026
Ready to ship a WhatsApp flow that doesn't break?
Public signup is open. The platform is free. AI features are paid separately.
