5.10 Workflow Import & Export

Pop Workflows not only allow you to build automation visually, but also support exporting the entire workflow as a JSON file, which can be imported, shared, backed up, and restored across any device or team.

With import & export features, you can:

• Save workflow versions
• Share with team members
• Build reusable industry templates
• Migrate workflows from development to production
• Sync workflows across multiple devices

This chapter introduces the complete export/import process, JSON structure, best practices, and common troubleshooting.

---

📤 1. Export Workflow

You can export the current workflow as a .json file.

How to export:

1. Open any workflow
2. Click the top‑right menu "⋯"
3. Select Export Workflow

The system will download a JSON file that includes:

• Node information (Nodes)
• Edge connections (Edges)
• Input / Output parameter definitions
• Initial global variables
• Layout references (if any)
• Module references
• Node configuration & PSL scripts

This ensures the workflow can be fully restored.

---

📥 2. Import Workflow

You may recreate any workflow using a local JSON file.

How to import:

1. Open the "Workflow List"
2. Click Import Workflow
3. Select a .json file
4. Pop will automatically restore the entire canvas

During import, the system will:

• Validate the file structure
• Automatically resolve conflicting node IDs
• Regenerate sequence numbers when needed
• Ensure compatibility with old versions

---

🗂 3. Workflow JSON Structure

The exported JSON contains all workflow information.

Below is a simplified example:

{
  "version": 2,
  "metadata": {
    "id": "wf_20240101_001",
    "name": "Auto Summary Generator",
    "created_at": "...",
    "updated_at": "..."
  },
  "nodes": [
    {
      "id": "node_1",
      "type": "input",
      "config": {},
      "position": { "x": 240, "y": 100 }
    },
    {
      "id": "node_2",
      "type": "llm",
      "config": {
        "model": "deepseek-chat",
        "prompt": "Please summarize the following content: {{input.text}}"
      },
      "position": { "x": 420, "y": 260 }
    }
  ],
  "edges": [
    {
      "id": "edge_12_1",
      "source": "node_1",
      "target": "node_2",
      "sourcePort": "out",
      "targetPort": "text"
    }
  ],
  "inputs": [
    { "name": "text", "type": "text", "required": true }
  ],
  "outputs": [
    { "name": "summary", "from": "node_2.output" }
  ],
  "layout": {
    "id": "layout_001",
    "widgets": [...]
  }
}

Meaning of each field:

Field	Description
version	Workflow JSON version number
metadata	Basic workflow metadata
nodes	All nodes in the workflow
edges	Connections between nodes
inputs	Input parameter definitions
outputs	Output parameter definitions
layout	Layout manager reference (if any)

---

🔄 4. Compatibility

Pop provides strong backward compatibility:

• Old JSON versions can be imported in newer Pop versions
• Missing fields are auto-filled with defaults
• Version mismatches trigger upgrade notifications
• Works across PC / Mac / Web environments

You can safely share workflows with any Pop user—even if their version differs.

---

🧠 5. Module Import/Export

If a workflow contains modules, export will:

• Inline module content (default)
• Or reference module IDs (coming soon)

During import:

• Modules are automatically created
• Sub‑workflow structures are fully restored

This enables reusable industry-level templates.

---

🧪 6. Using Workflows as Templates

After exporting, you may:

• Upload to team library
• Upload to Pop Template Center (future)
• Build industry solution templates

Examples:

• AI writing assistant
• SEO content generator
• Financial report analyzer
• Website log analyzer
• Knowledge base processing pipelines

Import/export enables Pop as a true "automation orchestration platform."

---

🚀 7. Migrating Workflows Between Computers

1. Export workflow on computer A
2. Copy JSON to computer B
3. Import workflow on computer B
4. Canvas, nodes, configuration, and layout fully restored

Perfect for:

• Multi-device work
• Team handover
• Migrating to new Pop environments

---

🛠 8. FAQ

❓ Node order becomes messy?

Pop automatically recalculates and normalizes node sequences.

❓ Import shows "Invalid JSON"?

Ensure the file wasn't manually modified or corrupted.

❓ Model configuration missing?

If the device lacks the same model, Pop will prompt to select one.

❓ Layout not restored?

Verify that the JSON contains the layout field (older versions may not).

---

🎯 9. Summary

Workflow import/export enables:

• Backup
• Migration
• Sharing
• Template reuse
• Cross‑device collaboration

With this capability, you can easily build team‑level and industry‑level automation systems.