Export Workflows

Workflows and String are shutting down on March 31, 2027. Learn more

You can export the workflows in a project to a ZIP archive. The archive has one JSON file for each workflow, which describes its triggers, steps, code, and control flow. Use it as a record of what you built, and as a reference when you rebuild your workflows on another platform. Export runs one project at a time. Export each project that has workflows you want to keep before all Workflows data is deleted on April 30, 2027.

Export a project

Open the project settings

Open the project in the Pipedream dashboard, then select Settings in the left navigation.

Start the export

Click Export Workflows at the bottom of the settings panel. Pipedream builds the archive in the background.

Download the archive

When the export finishes, the archive appears in the project’s File Store as project_export-<project_id>.zip. Select File Store in the project’s left navigation to download it.

Export writes the archive to the project’s File Store, so your plan must include File Stores.

Export again

Each project can have one export at a time. To export a project again (for example, after you change a workflow), delete the existing project_export-<project_id>.zip file from the File Store, then click Export Workflows again.

What’s in the export

The archive keeps the folder structure of your project:

project_export-proj_abc123.zip
├── manifest.json
├── sync-leads-to-sheets-p_abc123.json
└── Marketing/
    └── weekly-digest-p_def456.json

manifest.json

manifest.json lists every workflow in the project, including workflows that were not exported, so nothing is left out without a record.

{
  "schema": "project-export/2026.01",
  "workflow_schema": "workflow.json/2026.01",
  "project_hashid": "proj_abc123",
  "exported_at": "2026-10-01T17:00:00Z",
  "truncated": false,
  "truncated_reason": null,
  "limits": { "workflows": 500, "bytes": 268435456 },
  "workflows": [
    {
      "hashid": "p_abc123",
      "name": "Sync leads to Sheets",
      "path": "sync-leads-to-sheets-p_abc123.json",
      "status": "exported",
      "warnings": [
        "configured prop values are not exported; every step and trigger must be reconfigured after import"
      ]
    },
    {
      "hashid": "p_ghi789",
      "name": "Untitled workflow",
      "status": "skipped_never_deployed"
    }
  ]
}

Each workflow has one of these statuses:

Status	Meaning
`exported`	The workflow is in the archive at `path`.
`skipped_never_deployed`	The workflow was never deployed, so there is nothing to export.
`skipped_export_limit`	The export reached a limit before it got to this workflow.

Workflow files

Each workflow file contains the latest deployed version of the workflow:

Field	Contents
`name`, `description`, `inactive`, `settings`	Workflow metadata and settings.
`triggers`	Each trigger’s type (`source`, `http`, `timer`, `email`, or `form`) and configuration. HTTP, schedule, and form trigger settings are exported in full.
`steps`	Each step in order: its name, type, and either its code (for code steps) or the component key and version (for actions).
`deployments`	The steps inside each control flow branch, such as if/else and switch paths.

What’s not in the export

The export describes the structure of your workflows. It does not contain their data or credentials:

Configured prop values. Pipedream replaces the value of every prop you configured on a step or trigger with <redacted>. The prop names stay, so you can see what each step needs. Configured props can contain credentials, so no values are exported.
Connected accounts. Credentials and OAuth tokens are never exported.
Secrets and environment variables. Re-enter these values on your new platform.
Event history, data stores, and File Store files. Download any data you need separately. You can download files from the File Store directly.
Code for private multi-file components. The export includes the component key, but not its code. Keep a copy of the source for any private components you published.

The warnings list for each workflow in manifest.json tells you what you must reconfigure or re-enter.

Limits

One export includes a maximum of 500 workflows or 256 MB of workflow content, whichever comes first. If a project exceeds a limit, truncated is true in manifest.json, and the remaining workflows have the status skipped_export_limit. To export the remaining workflows, move some workflows to a different project and export each project.

Getting Started

Connect

Workflows

Platform

Additional Resources

Export a project

Export again

What’s in the export

manifest.json

Workflow files

What’s not in the export

Limits

​Export a project

​Export again

​What’s in the export

​manifest.json

​Workflow files

​What’s not in the export

​Limits

Export a project

Export again

What’s in the export

manifest.json

Workflow files

What’s not in the export

Limits