Pipedream Workflows Shutdown: Best Alternatives and How to Move

David AlfordOctober 11, 20268 min read

Pipedream is shutting down Workflows on March 31, 2027, and it will permanently delete every workflow, credential and OAuth token by April 30[1]. If you’re weighing Pipedream alternatives, the platform you pick matters less than what you save before then. The export tool leaves out more than most people expect, and some of it can’t be recovered once your account is gone.

Which platform fits depends on how much of your Pipedream work lived in code. Most of what follows applies wherever you move.

Is Pipedream shutting down?

Yes, partly. Pipedream Workflows and String shut down on March 31, 2027. Your existing workflows keep running until then, but Pipedream has stopped accepting signups and subscriptions and won’t ship new Workflows features. All Workflows data, including the credentials and OAuth tokens for your connected accounts, is permanently deleted by April 30, 2027.[1]

Pipedream’s stated reason is that it’s “focusing on being the integration layer companies rely on to connect AI to the outside world, and Workflows falls outside that focus.” Workday announced it would acquire Pipedream on November 19, 2025[2], and Workday’s results for the fiscal year that ended January 31, 2026 confirm the deal closed[3]. String, Pipedream’s AI agent builder, goes away on the same date as Workflows.

Monthly plans. You can cancel yourself from account settings whenever you’re done.
Annual plans. Contact Pipedream support for an early cancellation and a prorated refund.
Anything still active on March 31. Pipedream cancels it automatically and issues a prorated refund. You don’t have to do anything.

Do you need to move off Pipedream at all?

Only if you use Workflows or String. Pipedream Connect, the toolkit developers use to put integrations inside their own apps, isn’t affected. The Connect API, MCP servers and API Proxy stay fully supported, and Pipedream says that’s where its focus is going. If Connect is all you use, you can close this tab.[1]

Pipedream pricing reflects the change already. The pricing page now lists Connect plans only, from a free tier up to a $99 a month Startup plan and custom Business pricing[4]. The old Workflows plans are gone from it.

What the Pipedream export keeps, and what it drops

Pipedream’s export tool downloads one project at a time as a ZIP of JSON files covering triggers, steps, code, settings and non-secret props. It leaves out secrets, connected accounts, environment variables, event history, data stores, File Store files and the code for private multi-file components. You have to save those yourself before March 31.[5]

To run it, open a project, go to Settings and click Export Workflows at the bottom. The ZIP lands in that project’s File Store, where you download it. Your plan has to include File Stores, and each export stops at 500 workflows or 256 MB, whichever comes first.

Here’s what to do about each gap while your account still works:

Secrets. Secret props come out as <redacted>, and so does HTTP auth. Gather the real values from the services that issued them, or generate fresh ones, and keep them in a password manager.
Connected accounts. Only an authProvisionId survives, with tokens removed. Write down every app you’ve connected. You’ll sign in to each one again on the new platform.
Environment variables. They aren’t exported at all. Copy them out by hand.
Data stores. Also not exported. Write a one-off workflow that reads every key and writes it to a spreadsheet or database you control.
Event history and File Store files. Download anything you’ll need for audits or debugging now. After April 30 there’s nothing left to download.
Private multi-file components. Their code isn’t in the export. If it doesn’t already live in a repo you own, copy it into one.

Each ZIP has a manifest.json with a warnings list naming every step and prop you’ll have to re-enter or reconnect. Treat it as your migration checklist.

How to rebuild Pipedream workflows in TaskJuice with Claude or ChatGPT

There’s no direct importer for Pipedream exports, on TaskJuice or any other platform we’ve checked. What works is handing the JSON to an AI assistant connected to the TaskJuice MCP server. The assistant reads the workflow, finds matching TaskJuice steps, builds a draft and tests it. You reconnect accounts and approve the publish.

Export the project. You get one JSON file per workflow.
Connect TaskJuice to your assistant. In Claude or ChatGPT, add a new connector, paste your TaskJuice MCP URL, sign in and allow it to build workflows. The MCP setup guide walks through it.
Hand it one workflow. Paste the JSON and ask: “Rebuild this Pipedream workflow in TaskJuice. Use app steps where they exist and tell me anything you can’t match.”
Review the draft. The assistant validates the draft, test-runs steps against sample data and shows you a preview before anything goes live.
Finish the parts that need you. It hands back what only a person can do, mostly connecting accounts and pasting API keys, which is exactly the list the manifest warned you about.

Start with your simplest workflow. You’ll learn how close the first draft comes before you trust it with the one that bills customers.

What maps cleanly from Pipedream

HTTP triggers and $.respond(). A Webhook trigger plus a Respond step, which sets the status code, body and headers your caller gets back.
Cron triggers. The Schedule trigger, with cron expressions, intervals and time zones.
$.flow.delay and waiting on callbacks. The Delay step, and Wait for Event when a workflow has to pause until something else happens.
Data stores. Tables, with steps to find, create, update and delete rows.
Node.js steps that only reshape data. Expressions inside {{ }} or a Transform step, both of which speak JSONata.
APIs without a built-in app. The HTTP Request step, with headers, query, body, timeouts and retries.

What doesn’t port

Our Code step is deliberately narrow. It runs JavaScript in a sandbox with no npm packages, no network calls, no async/await and a 30-second limit. Python, Go and Bash aren’t supported. When a Pipedream step imports a package just to call an API, the assistant can swap it for an app step or an HTTP Request step. When it imports a package to do real work, like resizing images or running a pandas script, there’s no TaskJuice equivalent today.

The catalog is smaller too: 125 apps against Pipedream’s 3,000-plus. Anything we don’t cover goes through HTTP Request, which means setting up the API’s auth yourself.

When other Pipedream alternatives fit better

Pick TaskJuice if your workflows are mostly app steps, webhooks, schedules and small data fixes, or if you run workflows for clients. Pick something else if most of your Pipedream value lived in code. Windmill is the closest match to Pipedream’s code-first style, and self-hosted n8n runs JavaScript and Python with packages.

Windmill is scripts-first and open source, with Python, TypeScript, Go, Bash, SQL and more as first-class languages, and you can self-host it[6]. n8n’s Code node can import npm and Python modules on a self-hosted instance, though not on n8n Cloud, and its Sustainable Use License limits how you can use it commercially[7]. We’ve compared TaskJuice and n8n in detail in TaskJuice vs n8n Embed.

A month-by-month plan to March 31

Six months is plenty if you start now and painful if you start in March. Export and take inventory in October and November, rebuild your most important workflows by January, run old and new side by side in February, then cut over and pull your last data in March. Deletion follows on April 30.

October to November. Export every project. Save secrets, environment variables and data stores. List every webhook URL Pipedream gave you, the ones ending in m.pipedream.net, and which service each is pasted into. Those settings are easy to forget because they live in someone else’s dashboard.
December to January. Rebuild the workflows that matter most first. Rank them by what breaks if they stop, and work down the list.
February. Run both in parallel. Many services accept more than one webhook URL, so add the new one next to the old and compare runs for a week. Point scheduled workflows at a test destination until they match.
March. Swap the URLs for good, run one last export, and disconnect your accounts in Pipedream once nothing depends on them.
April 30. Pipedream deletes the rest.

Frequently asked questions

When is Pipedream shutting down?

Pipedream Workflows and String shut down on March 31, 2027, and all Workflows data is deleted by April 30, 2027. Pipedream Connect, its MCP servers and its API Proxy keep running.

Can I import Pipedream workflows into n8n, Make or Zapier?

Not directly. The export is Pipedream’s own JSON format, and it’s a blueprint, not something other tools load. You rebuild each workflow. An AI assistant connected to your new platform makes that much faster, because it can read the JSON for you.

Will my Node.js and Python steps work on another platform?

Rarely as they are. Pipedream-specific helpers like $.export, $.respond and steps.<name>.$return_value don’t exist anywhere else, so every step needs at least small edits. Code-first tools like Windmill keep most of your logic. On TaskJuice, plain JavaScript that reshapes data ports, and steps that import packages don’t.

Do I get a refund on my Pipedream subscription?

Yes. Annual subscribers can ask support for an early cancellation with a prorated refund, and any subscription still active on March 31, 2027 is cancelled and refunded on a prorated basis automatically.

Pipedream handled this better than most shutdowns: six months of notice, an export tool and automatic refunds. Use the time. An export done this week takes an afternoon, and one done in late March is a scramble.

If your workflows mostly move data between apps, try a rebuild on TaskJuice’s free plan with Claude or ChatGPT connected. It includes three active workflows and AI building over MCP, so you can see how close the first draft comes before you commit to anything.

[1] Workflows and String are shutting down on March 31, 2027, Pipedream documentation: pipedream.com/docs/workflows

[2] Workday signs definitive agreement to acquire Pipedream, Workday newsroom: newsroom.workday.com/2025-11-19-Workday-Signs-Definitive-Agreement-to-Acquire-Pipedream

[3] Workday fiscal 2026 fourth quarter results, SEC filing: sec.gov/Archives/edgar/data/1327811/000132781126000010/wday-01312026x991.htm

[4] Pipedream pricing: pipedream.com/pricing

[5] Export workflows, Pipedream documentation: pipedream.com/docs/workflows/export-workflows

[6] Windmill on GitHub: github.com/windmill-labs/windmill

[7] Code node, n8n documentation: docs.n8n.io/code/code-node/