Pipedream Workflows Shutting Down: What To Do

How to fix it

Try these in order — the most common fix is first.

1. 1. Export every project

   Copy steps
   1. Open the project, then Settings
   2. Run the export; a ZIP lands in the File Store
   3. Check manifest.json for warnings (limit 500 workflows or 256 MB; split larger projects)
   Did this fix it? Yes No

2. 2. Save what the export skips

   Copy steps
   1. Record secrets, env variables and connected-account details separately
   2. Dump data store contents with a workflow before shutdown
   3. Copy File Store files and anything you need from event history
   Did this fix it? Yes No

3. 3. Triage and migrate in waves

   Copy steps
   1. List workflows and retire unused or duplicate ones
   2. Rebuild the rest in n8n, Make, Windmill, Kestra or code
   3. Repoint webhooks and revoke old OAuth grants before March 31, 2027
   Did this fix it? Yes No

Symptoms

Notice that Workflows is being discontinued; workflows still run until then.

Why it happens

• Pipedream is refocusing on Connect and AI integration
• Workflows is in maintenance mode, closed to new signups (third-party reports)

This guide also covers

• pipedream shutting down
• pipedream workflows shutdown
• pipedream migration

Other Pipedream errors

• Pipedream Webhook URLs Stopping After Shutdown
• Pipedream Workflow Timeout Error
• Pipedream Out of Memory Error
• Pipedream Function Payload Limit Exceeded
• Pipedream Quota Exceeded and Runtime Quota Exceeded
• Pipedream Invalid Credentials or Access Token Expired
• Pipedream Event Queue Full and Rate Limit Exceeded
• How to Cancel Pipedream Subscription