run sub flow: Run Sub Flow lets a menu hub call booking, catalog, or support graphs without one giant spaghetti file. See why. Read how. Start here. Guide 2026.
run sub flow is the canvas job multi-location salon should ship this week. One canvas so huge nobody will edit the booking path? Wrong trigger or no Flow Builder wastes spend and nights.
Skip it if you only blast lists. multi-location salon needs a chat path, not a campaign.
Stay on this multi-location salon job: what to wire, what to delete, and the recovery—not a tour of every palette icon.
WAPilot implementers who sit in multi-location salon reviews would rather ship a thin v1 than hoard unpublished nodes.
Build leaf flows (book, shop, human) and publish them. Hub flow: keyword or new contact → menu → this node. That is enough setup talk for multi-location salon before the first heading.
this step lets a menu hub call booking, catalog, or support graphs without one giant spaghetti file. multi-location salon should treat that sentence as the job, not a slide title.
Sources: Meta’s messaging limits plus send-messages. Official Cloud API only—multi-location salon on a grey gateway is another product.
that component lets a menu hub call booking, catalog, or support graphs without one giant spaghetti file. On the canvas you place the canvas action, Interactive List, Trigger keywords. multi-location salon teams finish one job, then use Flow Builder when the customer sends a photo or a rant.
Publish buttons live in WhatsApp Flow Builder. Here we only design the multi-location salon graph with this path, Interactive List, Trigger keywords.
In this series — Part 3 of 5 (Logic). Previous: delay node. Next: send email. Series start: condition node.
Order: trigger, hello, Build leaf flows (book, shop, human) and publish them., then Flow Builder. That is v1 for multi-location salon.
A typical multi-location salon publish went wrong because one 80-node file; intern afraid to touch it. Changing the graph to hub + three sub-flows; booking edits no longer break FAQ stopped the screenshot pile-up.
Palette for this job: this step, Interactive List, Trigger keywords. If a node is not in that list, it waits for v2. Start with this: Build leaf flows (book, shop, human) and publish them. Then: Hub flow: keyword or new contact → menu → that component.
Unglamorous but required: Pass only what you must; keep leaf triggers off if the hub starts them. Without it, the canvas action, Interactive List, Trigger keywords sit unused and the customer still stalls.
Name flows clearly (hub_v1, book_clinic_v1). Test hub taps, not only leaves in isolation. If neither is on the canvas, multi-location salon will staff chaos from a phone gallery.
Attributed example, from a WAPilot multi-location salon workspace (2026): one 80-node file; intern afraid to touch it. hub + three sub-flows; booking edits no longer break FAQ
multi-location salon also split keywords so campaigns and this canvas could not greet the same inbound twice.
Rule sources: templates when silent; send-messages when the window is live; limits if multi-location salon nags. Read those before stacking Delay after this path.
How we know: WAPilot implementation plus inbox on official Cloud API—drip sequences, human handover, Flow Builder. multi-location salon here matches those queues and Meta’s public docs, using this node, Interactive List, Trigger keywords.
One sentence? Use drip sequences. A week of follow-ups? human handover. Branches and Flow Builder stay on the canvas for multi-location salon.
Do not park multi-location salon reminders at local 1am. Delay until morning beats a raw +24h from a midnight chat after this step.
Walk the false branch. A multi-location salon path that only works on perfect taps will strand the first typo after Hub flow: keyword or new contact → menu → that component.
Inside multi-location salon ops, they learned the hard way: one 80-node file; intern afraid to touch it. They recovered only after hub + three sub-flows; booking edits no longer break FAQ. That is the v1 bar for this journey.
Keep this node, Interactive List, Trigger keywords visible in the flow name so the next editor knows the job. First moves: Build leaf flows (book, shop, human) and publish them. Hub flow: keyword or new contact → menu → this step.
Stop it, staff the inbox for multi-location salon, template only when needed. Rating can take days. Delay nodes do not rewrite Meta’s window.
If both hub and leaf listen to hi, you double-fire. Usually leaves are started only via Run Sub Flow, not a second keyword.
Delay until a weekday, then a utility template if multi-location salon went quiet. Do not assume session is still alive after Run Sub Flow.
No. One thread, one clock. Two brands on one WABA share quality too. Split numbers before multi-location salon collides with another brand’s promos.
this journey only counts live. When you want Run Sub Flow on official Cloud API for multi-location salon, start a free trial on WAPilot.
ads to booking flow: Ads → catalog or booking: paid chat that sells the thing in the ad—slot or product—then human if needed. See why. Read how. Start here.
Read MoreStart automating your WhatsApp marketing today with WA-Pilot. Join thousands of businesses already growing with our platform.
Start Free Trialassign ads leads: Assign and tag ads leads: source label in the flow, Meta ad routing in Team Assignment, then sub-flow for the product. See why. Read how.
Read MoreCAPI in ads flow: Meta CAPI in an ads flow: fire Lead/Purchase after chat qualify so Ads Manager sees the WhatsApp truth. See why. Read how. Start here.
Read More