Skip to content
MoveWorkflows

Pipedream Workflows shutdown: dates, what closes, what stays

Updated 2026-10-21 · 3 min read

The Pipedream shutdown covers Pipedream Workflows and String, Pipedream's prompt-to-agent builder. Both stop on March 31, 2027, and all Workflows data is permanently deleted by April 30, 2027. Pipedream Connect (Connect API, MCP Servers and API Proxy) is not affected. The source is the banner on Pipedream's own Workflows documentation, which is the official announcement; we found no separate blog post.

Key dates

Date What happens Source
Already in effect No new sign-ups or subscriptions for Workflows Workflows docs
Until March 31, 2027 Existing workflows keep running normally. Maintenance mode, no new features Workflows docs
March 31, 2027 Workflows and String shut down. Subscriptions are cancelled automatically with a prorated refund Workflows docs
By April 30, 2027 All Workflows data is permanently deleted, including connected account credentials and OAuth tokens Workflows docs

Pipedream's docs do not give the date sign-ups closed, only that they are closed.

What shuts down

  • Workflows: triggers, code steps, pre-built actions, control flow, schedules, and the HTTP endpoints at *.m.pipedream.net.
  • String, Pipedream's builder that turns prompts into AI agents.
  • Workflows data: workflow definitions, event history, data stores, File Stores, environment variables and connected accounts used by workflows. All of it is deleted by April 30, 2027.

Pipedream gives its reason directly: the company is focusing on Connect, its integration layer for AI, and Workflows falls outside that focus.

What keeps working

Pipedream's notice says: "If you're using our Connect API, MCP Servers, or API Proxy, nothing changes for you." Connect settings and credentials are not deleted. The pricing page in the docs says the same: Connect is not affected and remains fully supported.

If you use both, separate them. A Connect integration inside your product is safe; a workflow in the same workspace is not.

What breaks on March 31, 2027

When Workflows stops, anything that depends on a running workflow stops with it:

  • Inbound webhooks. Stripe, GitHub, Shopify, form tools or your own app may be posting to a *.m.pipedream.net URL (triggers docs). Pipedream's notice doesn't say what happens to these URLs; expect requests to fail once workflows stop. Many senders retry for a while and then give up quietly.
  • Scheduled jobs. Nightly syncs, reports and cleanups stop running.
  • Email triggers. The @pipedream.net addresses created per workflow belong to Workflows; plan for them to stop delivering.
  • Workflow-backed APIs. If a frontend calls a workflow that responds with $.respond(), expect that endpoint to stop responding.

Make an inventory of senders now. The hardest failures to notice are webhooks from third-party services, because the errors show up on the sender's side, not yours.

What to do now

  1. Export every project. Project → Settings → Export Workflows, then download the ZIP from the project's File Store. The export needs a plan with File Stores; Pipedream's docs list File Stores for Advanced and above (File Stores docs). Guide: export Pipedream workflows.
  2. Copy what the export leaves out. Environment variables, secret values, data store records, File Store files and event history are not in the ZIP (export docs). Details: Pipedream data deletion.
  3. Pick a target platform. n8n is the closest fit for code-heavy workflows. Options are compared in Pipedream alternatives.
  4. Estimate the work. Our free report reads the export in your browser and marks each workflow green, yellow or red.
  5. Migrate and move senders to the new URLs, then turn off the Pipedream workflows. Walkthrough: migrate Pipedream to n8n.

About five months remain as of October 2026. Code steps with npm packages, many connected accounts and external webhook senders are what make a migration slow, so start with the workflows that carry money or customer data.

Is there an official migration tool?

Pipedream provides the export ZIP and says the shutdown gives you "a full six months to find an alternative and migrate." It does not name a replacement or a migration partner. n8n has no Pipedream importer either; it imports n8n workflow JSON. That gap is why third-party converters exist, ours included. The report and 1 workflow are free. Full export: $3 per workflow, $19 minimum — coming soon. See pricing.

moveworkflows is an independent tool and is not affiliated with Pipedream, Workday or n8n.

FAQ

When does Pipedream shut down?
Pipedream Workflows and String shut down on March 31, 2027. Existing workflows keep running normally until then. All Workflows data is permanently deleted by April 30, 2027.
Is Pipedream Connect shutting down?
No. Pipedream says nothing changes for users of the Connect API, MCP Servers or API Proxy. Connect settings and credentials are not deleted.
Can I still sign up for Pipedream Workflows?
No. Pipedream is no longer accepting sign-ups or subscriptions for Workflows. Existing workspaces keep working until March 31, 2027.
Do I get a refund for my Pipedream subscription?
Pipedream says it will automatically cancel subscriptions and issue a prorated refund, with no action needed. Annual plans can also be cancelled early through support.
What does Pipedream recommend instead?
Pipedream does not name a replacement. It provides an export tool so you can move workflows to another platform yourself.

Related

Sources