Import and Export Workflows
Export any workflow version as a JSON file for backup or reuse, and import workflow files into another workspace — with validation that catches problems before anything is created.
Workflows can be moved around as JSON files — export a version for safekeeping, then import it into another workspace, or restore it later. It's the fastest way to reuse a conversation you've already perfected.
Export a Workflow#
From the version history panel of any workflow, choose Export on the version you want. A JSON file downloads — you'll see a confirmation like "Exported v3 as bookings-workflow-v3.json."
The file contains the complete definition of that version: every step, connection, and setting. It does not contain customer data or conversation history — it's the blueprint, not the conversations.
Export your active workflows whenever you finish a significant change. A folder of JSON exports is a free, dependable backup — and your audit trail if you ever need to answer "what did the workflow look like in June?"
Import Workflows#
On the workflows list, select Import. The Import workflows dialog asks for a workflow export JSON file — one you previously exported.
Before anything is created, the file is validated:
- Structure — the file must be a genuine workflow export with valid steps and connections. Corrupted or hand-edited files that no longer parse are rejected with a clear error.
- Application match — a workflow exported from a different product can't be imported here. You'll see a message like "This file is for MyPetParlor; can't import into MyMicroFinance."
If validation passes, the workflow is created as a new draft — nothing goes live on import. Review it on the canvas, run it through the simulator, and publish when you're happy.
Imported workflows reference message templates by name. If the destination workspace doesn't have the same approved templates, validation will flag the missing ones before you can publish — create and approve them first.
Common Uses#
| Scenario | How |
|---|---|
| Backup before big edits | Export the active version, then edit a new draft freely — you can always re-import the export. |
| Copy between workspaces | Export from one workspace, import into the other, adjust anything workspace-specific, publish. |
| Restore an old behaviour | Export files are self-contained — import June's file and publish it to roll back to June's flow. |
| Share a starting point | Send a colleague your export so they don't start from a blank canvas. |