Pipedream Workflows shutdown: dates, what gets deleted, what to do

Pipedream Workflows and String stop running on March 31, 2027, and Pipedream will permanently delete all Workflows data, including the credentials and OAuth tokens of connected accounts, by April 30, 2027. Workflows has been in maintenance mode since September 30, 2026: existing workflows still run, but there are no new signups, subscriptions or features. Pipedream Connect is not affected.

This page collects the dates, what disappears and when, and a practical order of work for getting off the platform in time. The source for every date below is Pipedream's own shutdown notice.

Pipedream shutdown timeline

Date	What happens
September 30, 2026	Workflows enters maintenance mode. No new signups or Workflows subscriptions, no new features.
Now until March 31, 2027	Existing workflows keep running normally. The Export Workflows tool is available.
March 31, 2027	Workflows and String shut down. Subscriptions are canceled automatically with a prorated refund.
April 30, 2027	All Workflows data is permanently deleted, including credentials and OAuth tokens for connected accounts.

Pipedream says it is giving users "a full six months to find an alternative and migrate." Six months sounds generous until you count the work: every webhook sender has to be repointed, every connected account has to be authorized again somewhere else, and every code step has to run on a new runtime.

What is shutting down and what is not

Shutting down: Pipedream Workflows (triggers, steps, code steps, event sources attached to workflows, data stores, File Stores, GitHub Sync projects) and String.

Not affected: Pipedream Connect. The notice says that if you use the Connect API, MCP Servers or API Proxy, "nothing changes for you." Pipedream gives the reason directly: it is focusing on "being the integration layer companies rely on to connect AI to the outside world, and Workflows falls outside that focus." Workday announced an agreement to acquire Pipedream in November 2025.

Connect is an SDK and API for adding integrations to your own app or AI agent. It is not a hosted workflow builder, so it does not replace Workflows for most teams.

What gets deleted on April 30, 2027

Pipedream's wording is "All Workflows data will be permanently deleted by April 30, 2027." In practice that covers everything you built and stored in Workflows. The official export only saves part of it, so the table below matters more than the date.

Data	In the official export?	What to do before the deadline
Workflow structure: triggers, steps, step order, branches	Yes, latest deployed version	Export every project
Code of Node.js and Python steps	Yes	Included in the export
Configured props (channel names, sheet IDs, templates)	Yes, except secrets	Included in the export
Secret props and HTTP auth	No, shown as <redacted>	Collect the values from the original provider or your password manager
Connected accounts (OAuth tokens, API keys)	No, only an authProvisionId	Reconnect each app on your new platform
Environment variables	No	Copy the names. Secret values are never shown in the UI, so get them from the original provider.
Data stores	No	Export the records
File Store files	No	Download from each project's File Store
Event history	No	Save a few sample events per workflow for testing
Code of private multi-file components	No, only the component key	Keep your own copy of the source
Workflows that were never deployed	No (skipped_never_deployed)	Deploy them or copy the code by hand

All of this comes from Pipedream's Export Workflows documentation. Two details trip people up:

1. Data stores are not exported. If a workflow keeps state in a data store, such as deduplication keys, cursors or counters, you need to pull those records out yourself. You can view and edit them in the Data Stores dashboard, and Pipedream's docs include a sample code step that posts records to an external service in chunks.
2. The export itself lands in a File Store. The ZIP is written to the project's File Store, and Pipedream's File Stores FAQ says File Stores are only available on Advanced plans and above. Workspaces on Free or Basic may not be able to use the official export. See how to export Pipedream workflows for GitHub Sync and REST API alternatives.

Do not plan around the April window. Workflows stop running on March 31, 2027, and the notice only promises deletion "by" April 30. Treat March 31 as the real deadline for exports and data copies.

Billing during the shutdown

According to the notice, all subscriptions stay active until March 31, 2027. On that date Pipedream cancels them and issues a prorated refund with no action needed. Monthly subscribers can cancel earlier in account settings. Annual subscribers can contact support for early cancellation.

One caution before you cancel early: Pipedream's pricing docs say that when you downgrade, "any integrations that use features outside the new billing plan will be automatically disabled." If you are on Advanced or higher, export first and cancel second. Otherwise you may lose File Store access, and with it the official export.

What to do now: a migration checklist

1. Inventory your workspace. List every project and workflow, and mark which ones are still active. Inactive workflows are cheap to drop now and expensive to rediscover in April.
2. Export each project. Use Project, Settings, Export Workflows, then download project_export-<project_id>.zip from the File Store. One project per export, up to 500 workflows or 256 MB each. Details and alternatives are in the export guide.
3. Copy what the export leaves out. Secret values, environment variables, data store records, File Store files and a few sample events per workflow.
4. Size the work. Run the free migration report on your export. It runs in your browser and shows, per workflow, whether it converts automatically, needs an AI rewrite or a quick check, or needs manual work, plus the connected accounts and secrets you will have to recreate.
5. Pick a destination. For most Pipedream users that is n8n, either n8n Cloud or self-hosted. The Pipedream alternatives comparison covers when another platform fits better.
6. Convert and rebuild. Follow the Pipedream to n8n migration guide. Code steps need the most attention, especially on n8n Cloud, which cannot load most npm packages. See what breaks in code steps on n8n Cloud.
7. Recreate credentials. Authorize each app again on the new platform and re-enter secrets.
8. Run in parallel, then cut over. Point webhook senders at the new URLs one workflow at a time, compare results, then disable the Pipedream version.
9. Clean up. Disconnect accounts in Pipedream, and cancel the subscription only after everything is exported and switched.

A realistic schedule

The dates below are a suggestion, not a Pipedream requirement. They leave a month of buffer before workflows stop.

By	Milestone
End of November 2026	All projects exported, data copied, report reviewed, destination chosen
End of January 2027	Workflows converted and imported, credentials recreated
End of February 2027	Parallel runs done, webhook senders switched, Pipedream versions disabled
March 31, 2027	Pipedream Workflows stops running
April 30, 2027	Pipedream deletes all Workflows data

Webhook cutovers usually take longer than expected because the URLs live in third-party dashboards (Stripe, GitHub, form tools, internal apps) that someone has to log into and update. Start that list early.

Where to move

If your workflows are a mix of webhooks, schedules, app actions and JavaScript code steps, n8n is the closest match: it has a Webhook trigger with custom responses, a Schedule Trigger, If and Switch nodes, a Wait node and a Code node. The main gap is npm. n8n Cloud only lets Code nodes require crypto and moment, while self-hosted n8n can allow any installed package. The Pipedream vs n8n comparison walks through the differences that affect a migration.

How Workflow Exit helps

Workflow Exit is an independent migration tool. It is not affiliated with Pipedream, Workday or n8n.

• Free migration report. Upload your project export ZIP, a GitHub Sync repo or workflow JSON from Pipedream's REST API. The report runs entirely in your browser and lists triggers and their n8n equivalents, actions with and without automatic mapping, npm packages and whether n8n Cloud can run them, environment variables, redacted secrets, connected accounts to recreate, data stores and File Store data to save before April 30, 2027, an hours estimate, and a recommended destination.
• Paid conversion. Importable n8n workflow JSON for each workflow, with a compatibility layer for code steps, a CHECKLIST.md for credentials and cutover, and a bulk import script. Starter is $49 for up to 25 workflows, Team $149 for up to 100, Agency $399 for up to 500, and the first workflow is free. See pricing.

Start with the free report. It shows how much work stands between your workspace and the March 31 deadline.