Bring an Auto Flow into another workspace

Released 14 October 2026

Build a flow once and use it again: import an exported Auto Flow into another workspace, match what it uses to the ones there, and publish it.

What's new

• Import on the Auto Flows list. Pick a .flow.json file you exported from a flow's card, and it arrives as a new draft.
• A mapping page for everything the flow uses. Numbers, phone lines, templates, segments, people, forms, appointment services and the rest are each listed with their old name and the steps that use them. Anything this workspace already has is matched for you, and anything with the same name here is suggested.
• Links follow the move. Links that still name the old workspace can be switched to this one in one tick.
• Nothing goes out by mistake. Until every item has a match here, the flow shows Needs mapping, and it can't be published or test-run.
• Exports now carry names. A file you export says what each number, template and segment is called, so the person importing it knows what they are matching.

Worth knowing

• Some things need a check in the builder. Uploaded media, catalogue products, a Google spreadsheet or calendar, and request headers can't be matched automatically. The mapping page lists them.
• Send settings stay behind. Entry rules, the frequency cap and priority aren't in the file, so set them again on the imported flow.
• You can save partway. Your matches are kept, and you can also fix a step in the builder. Come back and save again to finish.