Import and Export

Workflows can be exported as JSON and imported back. This enables backup, sharing between team members, and moving workflows across projects.

---

Exporting a Workflow

1. Open the workflow on the canvas.
2. Click Export in the toolbar.
3. Choose Export as JSON.
4. A .json file downloads to your computer.

What's in the Export

The JSON export includes:

• All nodes (type, position, label, configuration)
• All edges (connections between nodes)
• Trigger configuration
• Agent node references (agent IDs from the source project)
• Expression strings

{
  "version": "1.0",
  "name": "Research Pipeline",
  "exported_at": "2024-01-15T10:30:00Z",
  "nodes": [
    {
      "id": "node_1",
      "type": "triggerNode",
      "position": {"x": 100, "y": 200},
      "data": {
        "label": "Trigger",
        "trigger_type": "manual",
        "default_input": "artificial intelligence"
      }
    },
    {
      "id": "node_2",
      "type": "agentNode",
      "position": {"x": 350, "y": 200},
      "data": {
        "label": "Research",
        "agent_id": "agent_abc123",
        "input": "{{trigger.output}}"
      }
    }
  ],
  "edges": [
    {
      "id": "edge_1",
      "source": "node_1",
      "target": "node_2"
    }
  ]
}

---

Importing a Workflow

1. Click Workflows in the sidebar.
2. Click the Import button (or the dropdown next to New Workflow).
3. Select your JSON file.
4. Preview the workflow structure.
5. Give it a name (defaults to the original workflow name).
6. Click Import.

The workflow appears in your list. Open it on the canvas to see the imported nodes.

Agent IDs from other projects won't resolve

When importing a workflow from a different project (or from a different user's export), agent node references (agent_id) will point to agents that don't exist in your project. These nodes show a ⚠️ indicator. You must select a replacement agent from your project's agents before running.

---

Use Cases

Backup

Export workflows periodically to keep local backups. Combine with a Schedule trigger + an http_request node to automate backups to S3, Notion, or another store.

Sharing

Share workflow designs with teammates or the community:

1. Export the JSON
2. Send via Slack, email, GitHub, etc.
3. Recipient imports into their project and replaces agent references

Moving Between Projects

1. Export from Project A
2. Import into Project B
3. Update agent references to Project B's agents

Version Control

Commit workflow JSON files to Git for version history:

git add workflows/research-pipeline.json
git commit -m "Add research pipeline workflow"

---

Batch Export

To export all workflows in a project at once:

1. Go to Workflows list.
2. Click Export All (bulk action menu).
3. Downloads a .zip file containing individual JSON files for each workflow.

---

JSON Schema

Workflow export files follow this schema:

interface WorkflowExport {
  version: "1.0";
  name: string;
  exported_at: string; // ISO 8601
  nodes: Node[];
  edges: Edge[];
}

interface Node {
  id: string;
  type: "triggerNode" | "agentNode" | "branchNode" | "loopNode" | "outputNode" | "humanLoopNode" | "noteNode";
  position: { x: number; y: number };
  data: Record<string, unknown>; // Type-specific configuration
}

interface Edge {
  id: string;
  source: string;     // Node ID
  target: string;     // Node ID
  sourceHandle?: string; // "true" or "false" for branch nodes
}