How to export Pipedream workflows

To export Pipedream workflows, open a project, go to Settings, click Export Workflows, and download project_export-<project_id>.zip from the project's File Store. The ZIP holds one JSON file per workflow plus a manifest.json. You need a plan with File Stores, and each export is capped at 500 workflows or 256 MB. Everything below comes from Pipedream's export documentation unless another link is given.

Export now, even if you migrate later. Pipedream Workflows stops on March 31, 2027 and its data is deleted by April 30, 2027.

Step by step

1. Open the project in Pipedream and click Settings in the left navigation.
2. Click Export Workflows at the bottom of the settings panel. Pipedream builds the archive in the background.
3. Click File Store in the project's left navigation.
4. Download project_export-<project_id>.zip.
5. Repeat for every project. The export works per project, not per workspace.

Each project holds one export at a time. To export again, for example after deploying changes, delete the existing ZIP and click Export Workflows again.

Plan requirement: File Stores

The export is written to a File Store, and Pipedream's docs say your plan must include File Stores. The File Stores page states they are "only available to Advanced plan and above subscribed workspaces", and marks the feature as Preview.

If your plan has no File Stores (Pipedream's docs don't state a plan tier for GitHub Sync, so check your workspace):

• GitHub Sync. If your project already syncs to GitHub, Pipedream serializes the workflows to YAML in that repository (GitHub Sync docs). Pipedream has not published a spec for this YAML yet. Our converter reads GitHub Sync repositories, but it finds no trigger configuration in them, so triggers are set up by hand. See Pipedream GitHub Sync to n8n.
• Manual copy. Open each workflow and copy the code steps, trigger settings and action props into a document. This is slow, but it works on any plan while your workspace is still running.

Limits

Limit	Value	What happens past it
Workflows per export	500	truncated: true; remaining workflows get skipped_export_limit
Workflow content per export	256 MB (268,435,456 bytes)	Same as above
Exports per project	1 at a time	Delete the ZIP to export again

If you hit a limit, Pipedream's suggestion is to move workflows into another project and export that project separately.

What is inside the ZIP

manifest.json at the root lists every workflow in the project, including those that were not exported:

• schema (project-export/2026.01) and workflow_schema (workflow.json/2026.01)
• project_hashid, exported_at, truncated, truncated_reason, limits
• workflows[] with hashid, name, path, status and warnings

The status is one of:

Status	Meaning
exported	The JSON file is in the ZIP
skipped_never_deployed	The workflow was never deployed, so there is nothing to export
skipped_export_limit	Over the 500 workflow / 256 MB limit

One JSON file per workflow, in the project's folder structure, with:

• name, description, inactive, settings
• triggers: each trigger's type (source, http, timer, email or form) and configuration
• steps: code for code steps, or the component key and version for actions, plus configured props
• deployments: the steps inside if/else and switch branches

Each file holds the latest deployed version. Undeployed edits in the builder are not exported, so deploy drafts you want to keep first.

What the export leaves out

Pipedream replaces a value with <redacted> when it is, or can be, a credential:

• props marked secret, including secret: true in code
• app props, which keep only an authProvisionId
• the auth object of HTTP request props
• props with no declaration, and system props such as $.service.db and $.interface.http

Prop names are always kept, and each workflow's warnings list tells you what to re-enter.

These are not exported at all:

Not exported	What to do
Secret values	Not visible in the UI; get them from the provider or rotate the keys
Connected accounts (credentials, OAuth tokens)	Reconnect each app on the new platform
Environment variables	Copy non-secret values from Settings → Environment Variables and the project's Variables; secret values are never shown again
Event history	No export exists; copy by hand what you need for records
Data stores	Export records separately; see data stores to n8n
File Store files	Download them from the File Store
Code of private multi-file components	Only the component key is exported; keep your own copy of the source

For data stores, Pipedream's data store docs include a sample action that posts records in chunks to an external endpoint. By default the sample deletes the keys it exported; switch that option off if you only want a copy.

Check the export before you rely on it

• Open manifest.json and look for anything other than exported.
• Read the warnings for each workflow and write down every secret you must re-enter.
• Count the workflows with code steps and npm imports; they take the most time.

Our free report does this in your browser: drop the ZIP and you get green, yellow or red for each workflow, the credentials to create, the npm packages and the webhooks to move. Nothing is uploaded.

Next step: convert to n8n

The export format is Pipedream's own, so n8n cannot import it as-is. Convert it to n8n workflow JSON, then import the JSON into n8n. The full process is in migrate Pipedream to n8n. The report and 1 workflow are free. Full export: $3 per workflow, $19 minimum — coming soon. See pricing.

moveworkflows is not affiliated with Pipedream or n8n.