Importing and Exporting Pipelines

Share pipelines as files, generate curl commands, and move pipelines between environments.

Exporting Pipelines

Export as JSON

What’s Included vs. Excluded

Why input data isn’t included:

• Keeps files small
• Protects sensitive data
• Makes pipelines reusable with different datasets
• Easier to share across environments

Importing Pipelines

Import from File

Import Conflicts

If a pipeline with the same name exists:

Sharing via Share Links

Generate Share Link

Share Link Management

Viewing shared pipelines:

1. Go to Sharing in the sidebar
2. See all pipelines you’ve shared
3. See share count and access logs

Revoking access:

1. Open pipeline menu
2. Select Share
3. Click Revoke all links
4. Confirm revocation

cURL Export

Generate cURL Command

Run any pipeline via HTTP using curl:

curl -X POST https://api.example.com/pipelines/execute \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "pipeline": {...},
    "input": {...}
  }'

cURL Options

Customize the command:

Example with file input:

curl -X POST https://api.example.com/pipelines/execute \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d @pipeline.json \
  --data-binary @input.json

API Execution

Execute via API

Run pipelines programmatically using the REST API.

Endpoint:

POST /api/pipelines/execute

Request body:

{
  "pipelineId": "pipeline_abc123",
  "input": {
    "your": "data",
    "goes": "here"
  },
  "options": {
    "timeout": 30000,
    "includeSteps": true
  }
}

Response:

{
  "success": true,
  "output": {...},
  "steps": [
    {"stepId": "step_1", "output": {...}},
    {"stepId": "step_2", "output": {...}}
  ],
  "executionTime": 1234
}

Authentication

Include your API key in the request header:

Authorization: Bearer YOUR_API_KEY

Rate Limits

Check response headers for rate limit info:

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 95
X-RateLimit-Reset: 1234567890

Pipeline Versioning

Export Specific Version

Each pipeline saves versions automatically. Export any version:

1. Open pipeline
2. Click Versions tab
3. Find the version to export
4. Click Export
5. Download .json file

Import as New Version

When importing, choose whether to:

• Create new pipeline — Fresh pipeline with imported version
• Add version to existing — Add as a new version of current pipeline
• Replace current version — Overwrite current version

Moving Between Environments

Demo to Dashboard

Move pipelines from demo (localStorage) to dashboard (cloud):

1. Export from demo:

   • Open pipeline in /demo/pipeline
   • Click Export
   • Download .json file

2. Import to dashboard:

   • Go to /dashboard/pipeline
   • Click Import
   • Select downloaded file
   • Save to cloud

Dashboard to Demo

Move pipelines from dashboard to demo:

1. Export from dashboard:

   • Open pipeline in /dashboard/pipeline/[id]
   • Click Export
   • Download .json file

2. Import to demo:

   • Go to /demo/pipeline
   • Click Import
   • Select downloaded file
   • Save to localStorage

Pipeline File Format

JSON Schema

{
  "version": "1.0",
  "name": "My Pipeline",
  "description": "Does cool things",
  "nodes": [
    {
      "id": "node_1",
      "type": "input",
      "position": {"x": 100, "y": 100}
    },
    {
      "id": "node_2",
      "type": "utility",
      "utilityId": "cleanup.clean-json",
      "config": {
        "removeNulls": true,
        "trimStrings": true
      },
      "position": {"x": 400, "y": 100}
    },
    {
      "id": "node_3",
      "type": "output",
      "position": {"x": 700, "y": 100}
    }
  ],
  "edges": [
    {
      "id": "edge_1",
      "source": "node_1",
      "target": "node_2",
      "sourceHandle": "output",
      "targetHandle": "input"
    },
    {
      "id": "edge_2",
      "source": "node_2",
      "target": "node_3",
      "sourceHandle": "output",
      "targetHandle": "input"
    }
  ],
  "metadata": {
    "createdAt": "2024-01-15T00:00:00Z",
    "modifiedAt": "2024-03-20T00:00:00Z",
    "version": 5
  }
}

Modifying Exported Files

You can edit exported .json files:

• Change pipeline name or description
• Modify node configurations
• Adjust node positions
• Add or remove nodes

Import back to apply changes.

Troubleshooting

Import Fails

“Invalid JSON format”

• Validate file syntax using a JSON validator
• Check for missing commas, brackets, or quotes
• Ensure file is complete (not truncated)

“Missing required fields”

• Verify file includes nodes and edges arrays
• Check that each node has id, type, and position
• Ensure edges reference valid node IDs

“Utility not found”

• Utility may not exist in this environment
• Check utility ID matches available utilities
• Replace with alternative utility if needed

Export Fails

“Pipeline too large”

• Pipeline exceeds file size limits
• Remove unnecessary nodes or data
• Split into multiple smaller pipelines

“Permission denied”

• You don’t have export permission
• Pipeline may be shared with you (not owned)
• Request owner to export instead

Next Steps

• API Guide — Complete API reference
• API Quick Reference — Common endpoints
• Management — Organize and share pipelines