Create and publish a Logic Flow

Create a Logic Flow when an inbound WhatsApp event should follow a predictable path. Start with one trigger, add the smallest useful response, and introduce branches only when the customer can clearly understand each choice.

Understand the building blocks

A trigger is the message or event that starts the flow. A node is one step, such as sending a reply or asking a question. Connections join those steps. A branch chooses the next step based on an answer or condition. A variable stores a value, such as the answer to a question, for a later step to use.

Create the draft

1. Open Logic flows and select Create flow.
2. Give the flow a name that describes the customer intent.
3. Open the editor and add an inbound trigger.
4. Add message, collection, data, routing, integration, or inbox nodes.
5. Connect each output to the intended next node.
6. Configure every required field and referenced resource.
7. Select Save draft.

Use the preview and validation feedback while editing. Keep button labels short, list choices distinct, and fallback paths explicit. A flow may contain up to 200 nodes and 400 connections, but a smaller flow is usually easier to operate.

Bind the account and numbers before publishing

1. Open the editor's Settings and find Flow settings.
2. Select the intended WhatsApp Business Account.
3. Choose the Assigned numbers that should use this flow.
4. Leave Active off and select Save settings.

The account and number assignment are part of the configuration that must be published. Confirm that each selected number is connected, permitted for your role and intended to use the flow handler. A number using Developer API handling follows that handling mode instead.

Publish and activate

Validation runs automatically in the editor. Review its issues panel and resolve blocking problems, then select Publish. Publishing creates an immutable version; it does not activate inbound handling.

After publishing the current configuration, open Settings again, turn Active on and select Save settings. Activation is refused when the exact current flow/account configuration is not published. If you change the account, assignments or graph, review validation and publish the intended configuration before activating it.

Confirm that the number, templates, forms, assignments and connected actions are available. If supporting resources cannot load, leave publication blocked and use the offered retry.

Assign the business account and sending number before selecting account-specific templates, catalog products or WhatsApp Flow forms. Select an eligible published form and map its submitted fields; a draft form is not a live form.

Test the customer path

Use a permitted test number and send the exact inbound trigger. Check each outgoing message, selected option, stored value, branch, and handoff. Verify that a human can see the context in Inbox after a handoff.

Test fallback and invalid input paths as carefully as the main path. If the flow uses a template, the current template and number quality rules still apply.

Next: Choose the right node or troubleshoot publication.