Use the integration actions shown in your editor for connected services. Long-running delays and A/B testing are not available.
WhatsApp flow builder
Learn how to build WhatsApp workflows without code.
Waaru's visual builder provides 28 authorable node types for inbound-responsive conversations. Design the trigger, message, collection, branch, data update, and human handoff as one versioned journey.
In one line
A WhatsApp flow builder is a visual editor for designing automated conversations. Waaru's current Logic Flow V2 release provides 28 deterministic node types, compiler diagnostics, published WhatsApp Flow forms, version-pinned runs, and human handoff.
A flow is difficult to operate when unexpected replies, invalid data, provider failures, and live edits have no explicit outcome. Review these paths before publishing, not after a customer finds them.
No-match handling needs an explicit fallback or human-inbox outcome.
Collected values need type validation, retry limits, and visible failure branches.
Published forms, templates, and sub-flows must stay pinned to reviewed resources.
Active conversations must not silently switch to a draft edited later.
28 node types in the registered release.
The node catalogue is shared by the strict canvas contract and the visual editor.
6 triggers for keywords, conversation entry, fallback, template replies, Click-to-WhatsApp referrals, and received media
9 message types for text, media, interactive options, catalogs, templates, WhatsApp Flows, locations, and contact cards
4 collection and data nodes for typed responses, variables, contact fields, and tags
5 routing nodes for conditions, short delays, jumps, pinned sub-flows, and explicit exits
3 inbox actions for assignment, status changes, and internal notes
1 integration node for approved connector actions
Route unexpected replies deliberately.
Fallback triggers catch conversations that do not match another published trigger. Collection nodes expose valid, wrong-type, retry-exhausted, and overwrite outcomes. If no automation matches, the canonical route is the human inbox.
Native WhatsApp Flows for structured data.
Choose a published WhatsApp Flow and map its submitted values into downstream flow or contact fields. The node exposes submitted and invalid-payload outcomes so malformed responses do not continue silently.
Keep active runs pinned to a published version.
New conversations start from the explicitly published snapshot. Existing runs resume against their pinned version, including pinned sub-flow references. Draft changes do not alter those runs. Traffic splitting and one-click rollback are not active dashboard capabilities.
Review starter flows before publishing.
The flow library copies a reviewed starter into your workspace as a draft. Configure its resources, inspect its branches, and resolve compiler diagnostics before publishing it for a WhatsApp number.
FAQ
Frequently asked questions.
What is a WhatsApp flow builder?
A WhatsApp flow builder is a visual editor for designing automated conversations. Waaru's current release covers triggers, messages, forms, typed collection, data updates, deterministic routing, and inbox handoff without writing code.
How does Waaru handle an unexpected reply?
Use explicit fallback triggers and validation outcomes. When no published automation matches, the message enters the human inbox. The current authenticated runtime does not invoke an AI model.
Does it support Meta's WhatsApp Flows (native in-chat forms)?
Yes. Select a published WhatsApp Flow, choose its screen, map supported prefill values, and store submitted answers as flow or contact variables.
Can I edit a flow that's already live?
Yes. Save a new draft version and publish it after validation. Existing runs stay pinned to their original version. Traffic splitting and one-click rollback are not active in the current dashboard.
Do I need to code anything?
No. Configure the available node types in the visual editor. API request and payment action nodes are not part of the current release.
Can a flow hand off to a human?
Yes. The handoff node pauses automation and assigns the existing conversation in the team inbox. The transcript and contact context remain attached to the thread.
Are templates included?
A starter library is available. Each copied starter remains a draft until you configure its resources, review its branches, and publish it.
What does the flow builder cost?
Deterministic flow access is free. AI features are paid separately. Each canvas supports up to 200 nodes and 400 edges.
What is the current release status?
Logic Flow V2 is available as the deterministic dashboard, API, and worker path. It remains available alongside Waaru's AI agent layer for journeys that need explicit state and branching.
