duplicate export clone: Duplicate, export JSON, clone flows across organizations—then change trigger and config, not the whole design. See why. Read how.
duplicate export clone is the canvas job two-city clinic should ship this week. Rebuilding the same booking graph for a second location by hand? Wrong trigger or no Booking Flow wastes spend and nights.
Teams like two-city clinic asked for a path without a 40-node novel. That is this article.
You'll see when Flow duplicate/export (product) is right and when human handover would have been enough for two-city clinic.
When this journey collided with campaigns in workspaces like two-city clinic, this is the rewrite that stuck.
Duplicate in-org for a second location. Export JSON if you must move orgs. That is enough setup talk for two-city clinic before the first heading.
Duplicate, export JSON, clone flows across organizations—then change trigger and config, not the whole design. two-city clinic should treat that sentence as the job, not a slide title.
two-city clinic already saw this fail: cloned flow still pointed at city A calendar The recovery was config swap checklist on every clone
Sources: send-messages (care window) and limits. two-city clinic hit both when this path kept talking after the chat went cold.
Duplicate, export JSON, clone flows across organizations—then change trigger and config, not the whole design. On the canvas you place Flow duplicate/export (product), Booking Flow, Trigger. two-city clinic teams finish one job, then use Booking Flow when the customer sends a photo or a rant. Official Cloud API session windows and templates still apply after publish.
Need palette click-path? Use WhatsApp Flow Builder, then return to this two-city clinic recipe.
In this series — Part 3 of 4 (Template Library). Previous: customize a template. Next: social channel flows. Series start: flow template library.
Five nodes beat fifteen. two-city clinic learned that after publishing dead ends on Flow duplicate/export (product).
Inside two-city clinic ops, they learned the hard way: cloned flow still pointed at city A calendar. They recovered only after config swap checklist on every clone. That is the v1 bar for this journey.
Keep Flow duplicate/export (product), Booking Flow, Trigger visible in the flow name so the next editor knows the job. First moves: Duplicate in-org for a second location. Export JSON if you must move orgs.
The step teams skip: Retarget keywords so they do not clash. two-city clinic paid for that skip with inbox screenshots. Put it on the canvas before you celebrate publish.
Finish like an operator: Re-select appointment/catalog IDs. Then Test the clone; IDs often break. Agents still work in a opt-in and opt-out settings after assign.
Attributed example, from a WAPilot two-city clinic workspace (2026): cloned flow still pointed at city A calendar. config swap checklist on every clone
They kept the flow on only after a test number survived typos, images, and “agent” for two-city clinic.
Rule sources: templates when silent; send-messages when the window is live; limits if two-city clinic nags. Read those before stacking Delay after Flow duplicate/export (product).
How we know: Meta developer docs plus WAPilot orgs already running Flow duplicate/export (product) for two-city clinic. We do not invent recovery hours.
human handover owns one-shot FAQs. Flow Builder owns the week-long nudge. This canvas owns the interactive two-city clinic job. Same keyword on two layers is how they doubled hellos.
This canvas is not a consent bypass. Opt-out on the number is opt-out in the flow. two-city clinic learned that loudly.
Preview is not Cloud API. two-city clinic must run on the live number. They found missing edges from a customer screenshot.
In a two-city clinic thread (2026), the failure was concrete: cloned flow still pointed at city A calendar. The rewrite that stuck was config swap checklist on every clone. Repeat that, rather than adding decorative palette icons.
two-city clinic only needed Flow duplicate/export (product), Booking Flow, Trigger on the happy path. Day-one order: Duplicate in-org for a second location. After the hello: Export JSON if you must move orgs.
Retarget keywords so they do not clash. Do that before you add another Condition. two-city clinic already tried the pretty version.
The adult move: Re-select appointment/catalog IDs. After that, Test the clone; IDs often break. Booking Flow remains the escape when the answer is messy. See also WhatsApp drip sequences.
Stop it, staff the inbox for two-city clinic, template only when needed. Rating can take days. Delay nodes do not rewrite Meta’s window.
Treat tokens as secrets. Rotate custom webhook tokens on the clone so city B does not share city A’s inbound URL.
Delay until a weekday, then a utility template if two-city clinic went quiet. Do not assume session is still alive after Flow duplicate/export (product).
No. One thread, one clock. Two brands on one WABA share quality too. Split numbers before two-city clinic collides with another brand’s promos.
this journey only counts live. When you want Flow duplicate/export (product) on official Cloud API for two-city clinic, 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