Developer · Meta Flow Editor

Stop writing Meta Flow JSON by hand.

SabNode's Meta Flow Editor is a visual designer for the JSON schemas that power WhatsApp Flows — multi-screen forms inside chat. Drag screens, bind components, validate against Meta's latest spec, and publish with versioning, rollback and a sandbox for end-to-end testing.

  • Visual builder for Meta Flow JSON
  • Live schema validation per Meta spec
  • Draft → review → published lifecycle
  • Bind data exchange endpoints inline
The problem

Authoring Meta Flow JSON is a tax on engineering

WhatsApp Flows are the most powerful surface Meta has shipped for business messaging — multi-screen forms with TextInput, DatePicker, Dropdown, CheckboxGroup and dynamic data binding. They also require you to author a strict JSON schema, register it with Meta, validate against a versioned spec that changes every quarter, and wire it to a signed data exchange endpoint that follows a request/response handshake with public-key encryption.

Most teams give up. They build the simpler interactive-message flow and miss out on the conversion lift of a real in-chat form. The teams that do not give up burn two engineer-weeks per Flow on JSON authoring, validation, signing, redeployment cycles and trial-and-error against the Meta sandbox. Every minor spec change breaks one of their screens and the entire pipeline has to run again.

SabNode's Meta Flow Editor collapses that work into a visual canvas. You drag screens, bind inputs to flow variables, write data exchange handlers as small TypeScript snippets, validate against the current Meta spec live, and publish with one click. Versioning, rollback and sandbox testing are first-class. Engineering keeps building product; the marketing team ships Flows on their own.

What it is

Meta Flow Editor, in depth.

The Meta Flow Editor is a canvas-style visual editor for the JSON that defines a WhatsApp Flow. Each screen is a rectangle on the canvas, with input components (TextInput, TextArea, RadioButtonsGroup, CheckboxGroup, Dropdown, DatePicker, Image), navigation buttons and conditional logic. As you edit, SabNode validates against Meta's latest published Flow schema and surfaces errors inline — wrong component for the action, missing required attribute, unsupported version — before you ever submit to Meta.

Data exchange — Meta's server-side handshake that lets Flows fetch dynamic content (a list of available appointments, a price calculation, an OTP) — is wired in two clicks. The editor exposes a typed handler where you write a small TypeScript function that takes the screen state and returns the next payload. SabNode hosts the encrypted endpoint, manages the keypair rotation, and exposes the resulting log to the dashboard. You never touch RSA key generation or AES-GCM ciphertext framing.

Lifecycle is enforced: Draft → Review → Published. A Draft is editable freely. A Review build is submitted to Meta's sandbox, where you can run the Flow end-to-end on a test number, watch every data exchange call and every state transition, and capture screenshots for QA sign-off. Publishing promotes the build to a versioned Published state on Meta; rolling back is a one-click revert to the previous Published version.

For agencies and multi-brand merchants, Flow templates are first-class. Author a Lead Capture Flow once with variables for brand colour, logo, success message and CRM mapping, then clone it across 30 client workspaces with workspace-specific bindings. Updates to the template can be propagated as a Draft to all clones for review before publishing.

Capabilities

Everything you get with Meta Flow Editor.

7 capabilities
01

Visual canvas

Drag screens onto an infinite canvas. Each screen renders a live preview of the WhatsApp Flow shell. Components are reorderable, conditional logic is drawn as edges between screens, and the underlying JSON is generated automatically.

02

Live schema validation

Every keystroke validates against Meta's current Flow JSON schema (v6.x and later). Errors are highlighted inline with the offending attribute, the expected type and a one-click "fix" for common mistakes like missing required keys.

03

Data exchange handlers

Write a small TypeScript function for the data exchange screen. SabNode hosts an encrypted endpoint with Meta-compliant RSA/AES-GCM handshake, manages keypair rotation and surfaces request/response logs in the editor.

04

Draft / Review / Published

Lifecycle stages enforce safe rollout. Drafts are editable, Review builds run on Meta's sandbox with a scannable QR for testing, Published versions are immutable until you cut the next version.

05

Versioning & rollback

Every Publish creates a new version. The previous version stays available for instant rollback. You can compare versions side by side and see exactly which screens or fields changed.

06

End-to-end sandbox

Test the Flow on a real WhatsApp test number with one tap. SabNode captures every screen transition, every data exchange call and the final completion payload, and shows them as a timeline in the editor.

07

Templates and cloning

Save any Flow as a template with parameterised fields. Clone into other workspaces with workspace-specific bindings. Updates to the template can be staged as Drafts across all clones for orderly propagation.

Use cases

Built for the way teams actually work.

Financial Services
Case 01

Lead capture for finance

A loan-origination team replaces a clunky landing page with a 4-screen Flow that captures name, PAN, income range and loan amount inside WhatsApp. Conversion rises 2.6× because customers never leave the chat.

Healthcare
Case 02

Appointment booking

A diagnostics chain ships a Flow with a dynamic DatePicker that fetches available slots via data exchange. Slot inventory updates in real time, double-booking is impossible, and the booking completes inside WhatsApp.

EdTech
Case 03

Course enrolment

An ed-tech runs a 5-screen Flow that scores the learner's level via a quick quiz, recommends a course, collects payment and provisions a learner account — all inside the Flow without redirecting to web.

Financial Services
Case 04

Insurance KYC

An insurer collects KYC photos and Aadhaar number through a Flow with conditional screens that adapt to the policy type. Documents upload via SabFiles, the Flow completes with a policy quote shown on screen.

F&B
Case 05

Restaurant reservation

A restaurant chain offers a Flow with venue selection, date, party size and seating preference. Data exchange pulls live availability from their booking system, and confirmation drops back into WhatsApp.

How it works

From signup to first send in minutes.

Meta Flow Editor is included on every SabNode workspace. No separate billing, no extra setup — flip it on from your workspace settings.

  1. 01

    Pick a template

    Start from a blank canvas or a template (Lead Capture, KYC, Booking, Survey). Templates ship pre-validated against the current Meta spec.

  2. 02

    Drag screens

    Add screens, drop in components, draw conditional edges. The JSON updates live and validation runs on every change.

  3. 03

    Wire data exchange

    Write a TypeScript handler for any screen that needs dynamic data. SabNode hosts the encrypted endpoint and keypair.

  4. 04

    Test in sandbox

    Scan a QR with your phone, run the Flow on Meta's sandbox, watch every state transition in the editor timeline.

  5. 05

    Publish & roll out

    Publish to a versioned production state. Use it in any flow builder node. Roll back in one click if something breaks.

Plays well with

Works with the tools you already ship on.

Meta WhatsApp Business PlatformAI StudioRazorpayStripeGoogle SheetsShopifySalesforceSabFiles
Frequently asked

Questions about Meta Flow Editor.

Can't find what you're looking for? Talk to our team.

Do I have to manage the data exchange keypair?
No. SabNode generates an RSA keypair per workspace, registers the public key with Meta and stores the private key in our managed KMS. Rotation is a one-click operation that publishes the new public key, dual-decrypts incoming exchanges during the cutover window and retires the old key safely.
Which Meta Flow JSON versions are supported?
All versions supported by Meta's public Flow Builder are supported here, with the current default being the latest stable. Drafts can target an older version explicitly if you need to keep parity with an existing Published Flow until your next planned release.
Can I write the JSON by hand if I prefer?
Yes. The editor has a JSON mode that shows the underlying Flow document with syntax highlighting and inline validation. You can paste JSON from another source, edit it directly, and switch back to the visual canvas — the two modes are always in sync.
How is Flow output passed to the rest of the system?
When a customer completes a Flow, the final response payload becomes a structured event on the SabNode conversation. Your flow builder can branch on the values, write them to the contact, drop them into a CRM, or fire downstream APIs — same as any other inbound event.
Can a non-engineer build Flows safely?
Yes, with guardrails. Workspace admins can lock the data exchange handler editor (which requires TypeScript) while leaving the visual canvas open for marketers. Publishes require a defined approver on enterprise plans, and lifecycle history is auditable per user.
What if Meta changes the schema?
SabNode tracks Meta's Flow schema releases, updates validation rules within 72 hours of publication, and surfaces a migration notice in any Draft that uses a deprecated attribute. Most schema changes are additive; the rare breaking change is handled by a one-click migration in the editor.
Is there a limit on screens or components per Flow?
Meta's current limit is 32 screens and a per-screen limit on components — SabNode enforces both at validation time. Most real-world Flows live well under those caps; if your Flow grows past them, the editor will suggest split points where you can branch into a second Flow.
Developer · Meta Flow Editor

Ship meta flow editor into production this week.

No credit card. No sales call required. Spin up a workspace, plug in a number, and your team is live in under an hour.