Guide · updated October 2026

How to export your Pipedream workflows (and what to do when the export fails)

Short answer. Open each project's Settings and use Export workflows. You get a ZIP with a manifest.json and one JSON file per workflow. It works one project at a time, skips workflows that were never deployed, and leaves out data stores, files and environment variables. If the export button fails with a file store error, ask Pipedream support to enable it for your account.

Step by step

Open the project in Pipedream and go to its Settings. The export lives in the project settings, not in the workflow list.
Click Export workflows and wait for the ZIP to download.
Repeat for every project. There is no single export for the whole account.
Open manifest.json and check which workflows were skipped (never-deployed workflows are listed but have no file).
Store the ZIPs somewhere safe. All Workflows data is deleted on April 30, 2027.

Pipedream's own instructions: Export Workflows.

Common problems

Problem	What to do
I don't see the export option	It is inside the project's Settings. Workflows created outside a project (the old v1 "workflows" tab) can't be exported this way, because the export relies on the project's file store.
The export fails with an error about the file store	Several users hit this in October 2026. Pipedream support fixed it by enabling the feature on the account: write to support@pipedream.com with your project ID and the error.
My export has no prop values	Exports made before early October 2026 left out the values of non-secret inputs. Pipedream added them later, so export again.
Some workflows are missing	Never-deployed workflows are skipped, and each export has a size limit. Deploy the ones you need, or split very large projects.
The `triggers` list is empty	It happens in some exports. Note how each workflow was started (webhook, schedule or app event) so you can set it up again.

What is in the export, and what isn't

Included: each workflow's steps (code steps and pre-built actions), the props you configured, triggers when present, and selected IDs with their labels (for example a SharePoint site or a Google Sheet name).
Redacted: secret values, connected-account credentials and OAuth tokens. Each app step keeps an authProvisionId, which tells you which account it used.
Not redacted: test data saved in code steps. Check it before sharing a ZIP with anyone.
Not included: data stores, File Store files, environment variables and event history. Download or copy them separately.

Export done? Convert it to n8n in your browser, nothing is uploaded.Convert my workflows

Next: how to migrate the exported workflows to n8n, or compare Pipedream alternatives.