Import and export a workflow (JSON)

Export any workflow as JSON and import it into another workspace or account, remapping channels, teams, and agents.

Jun 26, 2026

Watch this step in the video · Export and import

What it is and when to use it

Every Omnifox workflow can be exported as a self-contained JSON file and imported into another workspace, account, or kept as a backup. It's the fastest way to reuse an automation that already works without rebuilding it node by node.

Use it to:

  • Clone a workflow between your test and production workspaces.
  • Share a template with a teammate or another organization.
  • Save a backup before making big changes.

Before you start

  • You need edit permission for Automations in the workspace.
  • The JSON includes nodes, connections, the trigger, and the "Stop this workflow when the agent replies" setting, but it does not carry over other people's IDs (channels, teams, users, tags, AI agents): you remap those on import.

Export a workflow

  1. Open the workflow in the editor (Automations → your workflow).
  2. In the top canvas toolbar, click the Import / Export button.
  3. Keep the Export mode selected. You'll see the full JSON with a _meta block (version and export date).
  4. Click Copy to send it to the clipboard or Download to save the name-export.json file.

The export reflects the live canvas, including unsaved edits, so what you see is what gets exported.

Import a workflow

  1. Open (or create) the workflow where you want to load the content and click Import / Export.
  2. Switch to Import mode and paste the JSON into the Paste the JSON here… field.
  3. Choose a Strategy:
    • Add alongside the current workflow: appends the imported nodes to the ones you already have.
    • Replace the entire workflow: discards the current canvas and loads the imported one whole.
  4. Under Map external references, remap each ID to its equivalent in this workspace: Channels, Teams, Users, Tags, AI Agents, and Workflows.
  5. Apply the import and Save the workflow.

Verify

  • Check that every action node points to the correct channel, team, or agent in this workspace.
  • Confirm the trigger and, if relevant, the behavior settings.
  • Run a test of the workflow before activating it.

If it doesn't work

  • "nodes or edges missing in the JSON": the pasted text isn't a valid export; copy it again in full.
  • "Invalid JSON": it got truncated on paste or has unbalanced quotes; use the downloaded file instead.
  • A node does nothing after import: it likely kept an unmapped reference (nulled out for safety). Open it and pick the correct resource.

Tips

  • Version your exports with the date in the filename to keep a history.
  • Before a risky change, export: you get an instant "undo".

Related articles

Was this helpful?

Related articles

Message us on WhatsApp