Pipedream vs Zapier and Make

Pipedream vs Zapier used to be "developer tool vs no-code tool". With Pipedream Workflows shutting down on March 31, 2027, the question is whether Zapier (or Make) can take over workflows that were written for developers. For simple app-to-app automations it can. For code-heavy workflows the limits and pricing get in the way.

Comparison

	Pipedream Workflows	Zapier	Make
Status	Shuts down March 31, 2027	Active	Active
Code languages	Node.js, Python, Go, Bash	JavaScript, Python	JavaScript, Python (Code app, open beta)
npm / libraries	Most packages, installed on import	Public npm packages on paid plans	Custom libraries on Enterprise only
Code limits	Up to 750 s on paid plans	Plan-dependent; 6 MB I/O	30 s below Enterprise, 300 s on Enterprise
Webhook trigger	HTTP trigger	Webhooks by Zapier, not on Free	Custom webhook module
Billing unit	Credits (compute time)	Tasks	Credits
Self-hosting	No	No	No
Import from Pipedream	n/a	No	No

Sources: Pipedream code and limits; Zapier code steps, webhooks, pricing; Make Code app, webhooks, pricing.

Code steps

Pipedream treated code as the main building block. Zapier and Make treat it as an escape hatch:

• Zapier: Code by Zapier runs JavaScript or Python. Paid plans can add public npm packages. Input and output are capped at 6 MB, other limits depend on the plan, and code steps are rate-limited (10 requests per 60 seconds on Free) (rate limits).
• Make: the Code app runs JavaScript and Python, is in open beta, is available only on paid plans, and costs credits per second of execution. Below Enterprise a run is limited to 30 seconds and custom libraries aren't available.

A Pipedream step that imports three npm packages and runs for a minute won't move to Make below Enterprise, and may hit Zapier's plan limits.

Pricing model

Pipedream billed credits by compute time. Zapier bills per task: each successful action counts, while triggers and built-in tools such as Filter and Formatter don't. Make bills credits per operation, plus extra for code time. A webhook workflow with four actions costs four Zapier tasks per event. On n8n Cloud the same run is one execution, and on self-hosted n8n there is no per-run fee. Check current prices on each vendor's page; they change.

Webhooks

Pipedream gave every workflow an HTTP endpoint. Zapier's Catch Hook trigger needs a paid plan. Make's Custom webhook module accepts payloads up to 5 MB. Whichever you choose, every sender of a *.m.pipedream.net URL must be updated.

Imports

Neither tool imports Pipedream workflows. Zapier imports only its own JSON format, and only on Team and Enterprise. Make imports only its own blueprint files. A move to either is a rebuild.

When Zapier or Make is the right call

• Workflows are mostly pre-built app actions, with little custom code.
• Non-developers will maintain them.
• Volume is low enough that per-task or per-credit pricing stays small.

When n8n fits better

• Many Node.js or Python code steps.
• High webhook volume.
• You want self-hosting or a converter instead of a rebuild.

n8n has a converter path from Pipedream; Zapier and Make don't. Compare in detail: Pipedream vs n8n. All options: Pipedream alternatives. To estimate the work for n8n, drop your export into the free report. The report and 1 workflow are free. Full export: $3 per workflow, $19 minimum — coming soon. See pricing.

Not affiliated with Pipedream, Zapier, Make or n8n. Product names are used to describe them.