Build and publish deterministic Logic Flow V2 journeys.
The current release includes 28 node types and version-pinned execution. Use the integration actions shown in your editor for connected services. Long-running delays and A/B testing are not available.
Visual flow builder
Build WhatsApp workflows with a visual flow builder.
Build inbound-responsive WhatsApp journeys with visual triggers, messages, typed data collection, conditions, contact updates, reusable sub-flows, and human handoff. Compiler diagnostics block invalid drafts before they are published.
Inspect the trigger, data collection, branch, and confirmation as one connected journey. Select any stage to see its place in the workflow.
ExampleAppointment flow
28 node types across seven working categories.
6 triggers: keyword, conversation entry, fallback, template quick reply, Click-to-WhatsApp, and received media
9 message nodes: text, media, reply buttons, list, catalog, approved template, published WhatsApp Flow, location, and contact card
1 collection node for validated, typed customer responses
3 data nodes for flow variables, contact fields, and contact tags
5 routing nodes for conditions, short delays, jumps, pinned sub-flows, and explicit exits
3 inbox nodes for human assignment, conversation status, and internal notes
1 integration node for approved, opinionated connector read actions
Define every no-match outcome explicitly.
Use fallback triggers, validation branches, retry limits, and explicit exits to control unexpected replies. If no published automation matches, the conversation enters the human inbox instead of invoking an unconfigured model.
WhatsApp Native Flows as a first-class node.
Select a published WhatsApp Flow, choose its screen, prefill supported values, and map submitted answers into downstream flow or contact variables. Invalid or incomplete payloads follow a visible branch.
Publish versioned snapshots without changing active runs.
Each publish creates an explicit version. New conversations start from the published snapshot while active runs remain pinned to the version they entered. Compiler and resource diagnostics must pass before publication.
Start from a reviewed draft.
Copy a starter from the flow library, inspect every node, connect the required WhatsApp resources, and publish when the diagnostics are clear. Copied starters remain drafts until you review them.
FAQ
Frequently asked questions.
Do I need to know how to code?
No. The current 28 node types are configured in the visual editor. API request and payment action nodes are not part of this release.
Does it support WhatsApp Native Flows?
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 live flow without breaking it?
Yes. Save changes as a new draft version and publish after validation. Active runs stay pinned to their original version. One-click rollback and traffic-split testing are not active in the current dashboard.
Is there a node limit?
A Logic Flow V2 canvas supports up to 200 nodes and 400 edges. Deterministic flow access is free. AI features are paid separately.
What is the current product status?
The deterministic Logic Flow V2 path is available with public signup across the dashboard, API, and worker runtime. Real Meta delivery, the currently deployed release SHA, and representative-device behavior still require external launch verification.
