Skip to main content
Treat Flows like production code. Duplicate before risky edits, name clearly, and retire obsolete versions on purpose.

​
Duplicate for safe changes

1

Copy the live Flow

Open the Flow → use the builder submenu / duplicate control to create a copy.
2

Edit the copy

Make breaking changes only on the copy. Keep the original published and stable.
3

Test and publish the copy

Run Test Flow, then publish the copy.
4

Cut traffic over

Point Automation Rules, menus, drips, and buttons at the new Flow. Monitor, then archive the old one.

​
Copy a Flow to another workspace or page

If you operate multiple workspaces (for example multiple Facebook Pages / channel accounts), you can copy a Flow across them:
  1. Open the source Flow in the builder.
  2. Open the top-right submenu.
  3. Choose the destination workspace/page.
  4. Confirm the copy, then publish and reattach triggers on the destination.
Channel connections and some integrations may still need configuration on the destination account.

​
Naming conventions

Good names describe outcome + channel/context:
  • Onboarding — WhatsApp
  • FAQ menu — Omnichannel
  • Booking v2 — Telegram
Avoid Flow 3 and Copy of Copy of ….

​
Library hygiene

​
Next

Test and publish

Release checklist and mid-conversation risks.

Best practices

Broader Flow design standards.