Create a Logic Flow

Start with one inbound trigger and a useful response. Add branches only when the customer needs a choice.

Understand the building blocksCopy Anchor Link

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 draftCopy Anchor Link

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 publishingCopy Anchor Link

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 activateCopy Anchor Link

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.

Create a WhatsApp formCopy Anchor Link

Dashboard form creation requires the WhatsApp forms release to be enabled for your environment. Dynamic forms also require endpoint and encryption setup by your administrator. Meta validation and a real-device test are required before using a form with customers.

1. Open Automate → WhatsApp forms and create a static or dynamic draft under the same business account as your Logic Flow.
2. Add screens and questions. Give each answer a stable name so later steps can use it.
3. For dynamic forms, choose prefills from contact fields, Logic Flow variables, earlier answers or a connected service. Select an approved read action for each screen that needs business data and map its inputs. Dropdown choices can use selected fields from a service result.
4. Save the draft. For dynamic forms, have an administrator check and set up account encryption. An existing key from another endpoint needs administrator review.
5. Select Validate with Meta, inspect the preview, then Publish. Published forms are fixed; copy one to create an edited version.
6. Return to the WhatsApp Flow message node, select Refresh forms, choose the published form and map its answers to contact or Logic Flow variables. Connect the submitted route to the next step.

Connected actions inside a form read data. Run bookings, updates and other business actions after submission in Logic Flow. Completed answers are saved with the incoming message and can be viewed in Inbox or Chat. An incomplete form does not create a final response.

If a provider operation has an uncertain result, wait at least a minute and use Refresh Meta status. Keep the draft for recovery instead of creating a duplicate. A dynamic preview without an active Logic Flow conversation cannot read contact or service data.

Test the customer pathCopy Anchor Link

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.