Skip to main content
Waaru
Early access

Use the deterministic Logic Flow V2 path today.

Long-running delays, API requests, payment actions, catalogue messages, and A/B testing are not active in this release.

WhatsApp flow builder

Build deterministic WhatsApp journeys without writing code.

Waaru's visual builder provides 26 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 26 deterministic node types, compiler diagnostics, published WhatsApp Flow forms, version-pinned runs, and human handoff.

No credit card. No commitment.

26Authorable node types
200Nodes allowed per canvas
Native FlowsPublished Meta forms supported
Version-pinnedActive runs keep their snapshot

The problem

Where visual flows become fragile.

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.

26 node types in the registered release.

The node catalogue is shared by the strict canvas contract and the visual editor.

  • 5 triggers for keywords, conversation entry, fallback, template replies, and Click-to-WhatsApp referrals
  • 8 message types for text, media, interactive options, 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

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

Questions worth answering.

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.

Keep reading.

Compare

Evaluating platforms? Every claim cited, every price dated.

Ready to ship a WhatsApp flow that doesn't break?

Apply for founding access. No credit card. Cancel anytime.

See pricing