Pipedream Alternatives for Code-First Workflows

If you run workflows on Pipedream, the search for Pipedream alternatives stopped being optional. According to Pipedream's own shutdown notice, Workflows and String shut down on March 31, 2027. Existing workflows keep running until then, but the company says it is no longer accepting signups or subscriptions, and that all Workflows data, including stored credentials and OAuth tokens, is permanently deleted by April 30, 2027.

So the question is no longer "which tool is nicer?" It is "what keeps my code steps, my triggers, and my API glue running after March?" Short answers:

• Keep real code in the flow, self-hosted: n8n or Windmill.
• Keep it open source and approachable: Activepieces.
• Move to managed, with a code step when you need one: Zapier or Make.
• Your "workflow" is really background jobs in a TypeScript codebase: Trigger.dev.

None of these imports a Pipedream workflow. Plan on a rebuild, and start with the export.

What happened to Pipedream

Two separate facts, easy to blur together.

The ownership change. Workday signed an agreement to acquire Pipedream on November 19, 2025, describing it as an integration platform for AI agents with more than 3,000 pre-built connectors. Workday's fiscal 2026 results release, dated February 24, 2026, states that Workday closed the acquisition.

The shutdown. Pipedream's notice gives its own reason: the company says it is focusing on being the integration layer companies rely on to connect AI to the outside world, and that Workflows falls outside that focus. The notice does not mention the acquisition, so this article does not link the two. Draw your own conclusion, but cite the notice, not a guess.

What is not affected, per the same notice: Pipedream Connect, the Connect API, MCP servers, and the API proxy remain supported. If you embed Pipedream's integrations inside your own product, that is a different decision from the one this article covers, and none of the tools below is a one-for-one replacement for it.

Pipedream's pricing documentation also carries the shutdown warning, so check the pricing page for the current state before you cancel or renew anything. Subscriptions stay active until March 31, 2027, then are automatically cancelled with a prorated refund, according to the notice.

Quick comparison

Billing models change often, so the table gives shapes rather than numbers. Each vendor's pricing page is the source of truth.

Pick by what you used Pipedream for

If you wrote code steps and want to keep writing them

n8n is the closest in feel for most people. Its Code node runs JavaScript, and Python is available too. There is a catch worth knowing before you migrate: on a self-hosted install you can import built-in and external npm modules, while n8n's docs say that on n8n Cloud you cannot import external npm modules. If your Pipedream steps lean on npm packages, that decides between self-hosting and Cloud.

n8n's source is public under the Sustainable Use License, which allows internal use and self-hosting. It is source-available rather than OSI open source, and the license restricts offering it to others as a hosted service. n8n's hosting docs say that without a license key it runs as the free Community edition, and that paid keys unlock the Business and Enterprise features. If you want the long version, our n8n alternatives guide covers where n8n itself falls short.

Windmill goes further toward code. Its docs describe scripts in TypeScript, Python, Go, Bash, SQL, Rust and more, wired into flows and UIs. Its own README lists Pipedream among the tools it positions itself against. The licence needs a careful read: the README says the repository is AGPLv3, but the Community Edition binaries and Docker images also contain proprietary code under separate terms. Internal use is permitted; reselling those builds or running them as a managed service for others needs an agreement. A binary built from source without the enterprise feature flag is a separate route: the README says it is AGPLv3, and that you can comply with the AGPLv3 terms or get a commercial licence. For a company automating its own operations, the official builds are usually fine. An agency hosting it for clients should compare the source-built AGPLv3 route with a commercial licence.

If you want open source and a gentler handover

Activepieces is the pick when the person inheriting your workflows is not a developer. Flows are visual, with inline TypeScript available for the harder steps. The repository says the Community Edition is MIT-licensed, with enterprise features under a separate commercial licence. Integrations are written as TypeScript pieces published as npm packages, so a developer can add one for an API that has no connector. The project's own pages quote different integration counts in different places, so check the current library for the specific apps you need rather than trusting a headline number. We cover it further in Activepieces alternatives.

If you want managed hosting and fewer decisions

Zapier has the widest app directory, and its JavaScript Code step runs Node.js 22 in a sandbox, with Python available as a separate Code step. The limits depend on your plan, and Zapier's documentation says adding public npm packages is available only on paid plans. It is a managed service, so there is nothing to self-host. Zapier's task usage rates page splits steps three ways: built-in tools such as Formatter, Filters, Paths, Delay, Looping and Sub-Zaps use no tasks; a standard app action or Code step uses one task; and some types cost more, such as Lead Router at five tasks, Code runtime beyond the plan allowance at one task per extra 30 seconds, and AI by Zapier at three or five tasks per AI step and per tool call on Advanced or Premium models. Long workflows full of app actions and AI calls cost more than they would on a per-execution model. See Zapier alternatives for the wider picture.

Make has a Make Code app that runs JavaScript or Python inside a scenario. As of this writing its docs mark it as open beta and available on paid plans, with a 30-second execution limit on Core, Pro and Teams plans, and warn that functionality and pricing may change. That is fine for data shaping and light logic. It is not where you put a long-running job. Make bills in credits, and its visual canvas is better at branching and iterating over data than most code-first tools.

If your "workflow" was really background jobs

Some Pipedream workflows were never integration glue. They were scheduled scripts with retries. Trigger.dev is built for that: its repository describes an open-source platform for building AI workflows in TypeScript, with tasks that live in your own codebase as ordinary functions, plus queues, retries, and observability. It is Apache-2.0 licensed, can be self-hosted with Docker Compose or Kubernetes, and also runs as a managed cloud. The trade is that you give up the library of ready-made app connectors. You write the API calls yourself.

A tool that is already gone

You will see Relay.app on older "Pipedream alternatives" lists, usually as the friendly option with human approval steps. Its site now says it shut down in September 2026, and that all accounts, workflows, and run history were permanently deleted. Do not plan a migration to it. It is a reminder to check the date on any comparison, including this one, and to read the vendor's own page.

Migration checklist

Pipedream publishes an export tool that downloads each project's workflows as a ZIP of JSON files, one file per workflow, with a manifest. Use it early, and know what it leaves out:

1. Export every project. It is one project at a time, and each export is capped at 500 workflows or 256 MB.
2. Expect redacted values. Secret props and connected account credentials are not exported, so list every connection you will have to re-authorise.
3. Note what else is missing. Per the docs, environment variables, event history, data stores, and File Store files are not part of the export.
4. Back up private component source separately. If a workflow uses a private multi-file component, the export records the component key, not its code. Keep your own copy of that source before the shutdown.
5. Inventory by trigger type. Webhooks, schedules, and app event triggers each map differently. Webhook URLs change when you move, so every sender needs updating.
6. Rebuild the riskiest workflow first. The one with the most code and the most credentials tells you whether your chosen tool is viable.
7. Run both in parallel for a week while Pipedream is still alive. You have until the shutdown date, so use the overlap.

Where Taku fits

Taku is not a Pipedream replacement, and it will not host your webhook endpoints. It solves a different problem: you found an AI setup or workflow someone else already got working, and you cannot get it running yourself. Taku is an AI-native desktop workspace where you mirror a working app or workflow, run it, and remix it, without cloning a repo or configuring an environment first. Taku is in Beta, and the Mac app is available now. The free app library shows what that looks like. If your Pipedream workflows were mostly "take a document, have an AI process it, save the result", a mirrored app may cover that without a server. If they were production integrations with SLAs, use one of the tools above.

FAQ

Is Pipedream shutting down?

Part of it. Pipedream's notice says Workflows and String shut down on March 31, 2027, and that signups and subscriptions are closed. It also says Pipedream Connect, the Connect API, MCP servers, and the API proxy are not affected.

Was Pipedream acquired?

Yes. Workday announced a definitive agreement in November 2025, and its February 2026 results release says the acquisition closed. Pipedream's shutdown notice does not mention the acquisition.

What is the best free Pipedream alternative?

The self-hosted options, n8n Community edition, Activepieces, and Windmill, avoid per-run vendor fees, though you pay for the server and the person who maintains it. Check each project's licence for what "free" covers. n8n's terms and Windmill's official builds both restrict reselling them as a hosted service; a Windmill binary built from source without the enterprise flag falls under AGPLv3 instead.

Which alternative is closest to Pipedream for developers?

n8n and Windmill. n8n gives you a visual canvas with a Code node, and Windmill treats scripts as the primary unit. If your steps depend on npm packages, test that on your chosen deployment first, because n8n Cloud does not allow external npm modules.

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

Pipedream's export tool produces JSON for reference and rebuilding. We found no vendor documentation describing a direct import of that format, so assume a manual rebuild.

Does anything replace Pipedream Connect?

That is a separate product, still supported according to Pipedream. It exists for embedding integrations in your own app. The tools in this article are for running your own automations, so evaluate them separately.