Reuse a published Logic Flow

Use a published sub-flow when several customer journeys need the same bounded sequence. Define what it accepts and what it returns before attaching it to a parent flow.

Prepare the child

1. Create the reusable Logic Flow and add the nodes needed for its task.
2. Open Sub-flow entries, select Add internal entry, name it and choose its Start at node from the non-trigger nodes. Declare the typed inputs the parent must supply.
3. Declare the outputs that the parent needs. Ensure the child sets their variables and ends through Exit with Outcome: Completed. A failed/cancelled exit or invalid output returns through the parent’s failure path.
4. In the child’s Settings > Flow settings, save the same WhatsApp Business Account and relevant Assigned numbers that the parent will use. Leave the child’s public Active toggle off unless it separately needs an inbound trigger.
5. Resolve validation issues and publish the child. An unpublished draft cannot serve as the parent's pinned published version.

Keep the task small enough to test separately. For example, a child can collect enquiry details and return the validated values. Do not treat the return as confirmation of an external booking unless an authorized action actually created that booking.

Connect the parent

1. Add Sub-flow to the parent and use the Published sub-flow selection field.
2. Choose the published child and its entry point.
3. Map each input from an appropriate parent value.
4. Map the child's declared outputs to the parent's destination variables.
5. Connect both success and failure paths.
6. Validate and publish the parent, then test the complete customer journey.

Check both the message sequence and the values returned to the parent. Missing input, an unavailable referenced resource and an unexpected customer answer need deliberate handling.

Upgrade deliberately

The parent is pinned to the selected published child version. Editing or publishing the child does not silently upgrade the parent's configuration. Select Upgrade to v… for the intended child version. Changing the selected version or entry point clears mappings, so rebuild and check the input/output mappings before republishing the parent.

Keep resources used by an older in-flight journey available until the relevant work has finished. Use publication troubleshooting if a referenced version or resource cannot be loaded.

This guide concerns Logic Flows. Automation sub-flows are not available in the current Automation editor.