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, configured props, 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": [
        "step send_message: secret prop api_key was omitted from the export and must be re-entered 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. Source triggers include their configured props.
`steps`	Each step in order: its name, type, either its code (for code steps) or the component key and version (for actions), and its configured props.
`deployments`	The steps inside each control flow branch, such as if/else and switch paths.

Configured props

The export includes the values you configured on each step and source trigger, such as a channel name, a spreadsheet ID, or a message template. Pipedream replaces a value with <redacted> when it is, or can be, a credential:

Prop	What the export contains
Secret props	`<redacted>`. This includes props declared `secret: true` in code steps.
App props (connected accounts)	Only the `authProvisionId` of the connected account. Tokens and other credentials are removed.
HTTP request props	The request configuration. The `auth` object (basic auth and bearer token) is `<redacted>`.
Props with no declaration	`<redacted>`, because Pipedream cannot tell whether the value is a credential.
System-managed props (for example, `$.service.db` and `$.interface.http`)	`<redacted>`. These values are created when you deploy.
All other props	The value as you configured it.

The prop name always stays in the export, so you can see what each step needs.

What’s not in the export

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

Secret prop values. See Configured props. Re-enter these values on your new platform.
Connected accounts. Credentials and OAuth tokens are never exported. The authProvisionId identifies the account only inside your Pipedream workspace, so connect the account again on your new platform.
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 names each step and prop that you must re-enter or connect again.

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

Configured props

What’s not in the export

Limits

​Export a project

​Export again

​What’s in the export

​manifest.json

​Workflow files

​Configured props

​What’s not in the export

​Limits

Export a project

Export again

What’s in the export

manifest.json

Workflow files

Configured props

What’s not in the export

Limits