Make vs Zapier: Per-Operation vs Per-Task Cost, Run at Real Volume

Both automate the same apps. They bill on completely different units — and at 50k+ runs a month that difference is the whole decision. Here's the cost math with sourced numbers, plus the polling trap nobody puts on the pricing page.

by Ivar Berg · updated May 2026 · how we test

Some links are affiliate links: if you sign up through them we may earn a commission, at no extra cost to you. It never affects our ranking or the cost-math. Full disclosure.

The verdict: If your workflows are simple (1-3 actions per run) and you hate surprise bills, Zapier's per-task model is predictable but expensive at volume. If your workflows are multi-step, Make is dramatically cheaper per unit of work — Core is $9/mo for 10,000 credits versus Zapier's $19.99/mo Professional base — but Make charges for every module action AND for polling triggers that fire on a timer whether or not there's new data. That polling tax is the catch: a 1-minute poll runs roughly 43,000 checks a month before any real work happens. Net: pick Make for cost efficiency on busy multi-step automations; pick Zapier if you want triggers that cost nothing and a bill you can predict. And if you're running 50k+ runs/month and can manage a VPS, self-hosted n8n makes both look expensive — unmetered executions on a $3-12/mo server.

The unit of billing is the whole story

Make and Zapier connect the same apps and solve the same problems. The difference that actually shows up on your invoice is what each one counts.

Zapier bills per task. A task is one completed action. The trigger that starts a Zap — the thing watching your inbox or your form — does not consume a task, and polling for new data is also free. So a 3-step Zap that runs 1,000 times costs roughly 3,000 tasks, not 3,000 plus trigger checks. (zapier.com/pricing, as of 2026-05-30)
Make bills per operation (credit). Every module action is one credit. Critically, polling triggers consume operations on a timer even when there's no new data. (make.com/pricing, as of 2026-05-30)

That single design choice flips the cost comparison depending on how your automations are shaped. Many simple workflows favor Zapier's free triggers; busy multi-step workflows favor Make's cheaper per-unit price — until polling enters the picture.

The polling tax — Make's hidden cost

This is the line item that doesn't appear on the pricing page. Make's polling triggers check for new data on a fixed interval and burn an operation each time, regardless of whether anything changed. The math follows directly from the interval (1,440 minutes in a day):

A 5-minute poll = 288 checks/day = ~8,640 operations/month on the trigger alone.
A 1-minute poll = 1,440 checks/day = ~43,000 operations/month before a single real action runs.

Zapier doesn't charge for this — its triggers and polling are free. So a low-volume-but-high-frequency-polling scenario can actually cost more on Make than the per-operation price suggests. Practical move on Make: use instant (webhook) triggers wherever the source app supports them, and widen poll intervals to the longest your use case tolerates.

Cost at 5k / 50k / 500k runs per month

Numbers below are sourced to the vendor pricing pages where flat-published; where a figure is slider-priced and not flat-published, it's flagged as an estimate. Note the unit mismatch is real — a Zapier "task" (one action) is not the same as a Make "operation" (one action, plus polling) or an n8n "execution" (one full run). Normalize to your steps-per-run before comparing.

5,000 runs/month

Make: $9/mo Core — 10k credits covers 5k single-action ops with headroom. Cheapest hosted option. (make.com/pricing)
Zapier: ~$73.50-139/mo Professional (slider tier — estimate).
n8n Cloud: EUR 50/mo Pro (~$54) — 10k execs; Starter (EUR 20) caps at 2,500 so 5k needs Pro. (n8n.io/pricing)
n8n self-host: ~$3-5/mo VPS, executions unmetered.

50,000 runs/month

Make: ~$40-50/mo Core, scaled past the 10k base (slider-priced estimate — confirm on the live slider).
Zapier: several hundred $/mo on Team ($69 base + the 50K task tier). Exact sticker not flat-published.
n8n Cloud: EUR 667/mo Business (~$720) — includes 40k execs, so 50k means overage or Enterprise. (n8n.io/pricing)
n8n self-host: ~$5-12/mo VPS. This is the wedge: ~$12 self-host vs n8n Cloud's EUR 667.

500,000 runs/month

Make: ~$300-340/mo (slider-priced estimate — not confirmed on the live slider).
Zapier: high, trending toward the ~$5,999/mo ceiling; likely Enterprise/custom in practice (estimate).
n8n Cloud: custom Enterprise, not public.
n8n self-host: ~$9-18/mo VPS with queue mode, executions still unmetered.

Affiliate disclosure: we earn a commission if you start a paid plan via our Make or n8n Cloud links. It costs you nothing extra and doesn't change the math above. Zapier and other tools are editorial-only here — no affiliate relationship.

Try Make (lower per-operation price on multi-step runs) · Try n8n Cloud (per-execution, predictable)

The n8n escape hatch (and its license catch)

For the operator running 50k+ runs who can manage a $4-20 VPS, the real cost story isn't Make vs Zapier — it's self-hosted n8n. The Community Edition is free software under a fair-code / Sustainable Use License, executions are unmetered, and you pay only for the server: roughly $3-5/mo raw, ~$7/mo managed. (github.com/n8n-io/n8n, 2026-05-30)

The trade-off is real and worth stating plainly: you take on ~1-3 maintenance hours a month and the DevOps responsibility (updates, backups, queue mode at high volume). It's also source-available, not OSI open source — a distinction the licensing-sensitive should note.

"So yeah, you can use n8n for free, but that doesn't make it open source. It is a source available license."
— tinco, Hacker News, 2025-05-06

If you'd rather not run a server, n8n Cloud gives you the same per-execution billing managed for you — cheaper per run than Make or Zapier on multi-step workflows because one execution covers any number of steps.

Which one to pick

Pick Zapier if your workflows are simple (1-3 actions), you poll frequently, and you value free triggers plus a predictable bill over raw cost efficiency.
Pick Make if your workflows are multi-step and you want the lowest per-unit price — just budget for polling and use webhook triggers where you can. Start on Make Core ($9/mo).
Pick n8n self-host if you're past ~50k runs/month and can own a VPS; nothing else competes on cost at that scale.
Pick n8n Cloud if you want per-execution economics without the DevOps. Per-execution, managed.

The honest summary: there's no universal winner. The unit of billing — task vs operation vs execution — interacts with your steps-per-run and trigger frequency, and that interaction decides the bill more than any sticker price does.

What real users say

So yeah, you can use n8n for free, but that doesn't make it open source. It is a source available license.
— tinco, 2025-05-06, via Hacker News

FAQ

Is Make always cheaper than Zapier?

No. Make's per-operation base price is much lower ($9/mo Core for 10,000 credits vs Zapier's $19.99/mo Professional base), but Make charges for polling triggers that fire on a timer — a 1-minute poll runs ~43,000 checks/month before real work. Zapier's triggers and polling are free. For simple, high-frequency-polling workflows Zapier can win; for busy multi-step workflows Make is usually cheaper.

What's the difference between a task, an operation, and an execution?

A Zapier task is one completed action (triggers and polling don't count). A Make operation is one module action, plus polling-trigger checks. An n8n execution is one full workflow run regardless of step count. Because the units differ, you must normalize to your own steps-per-run before comparing prices.

How much does Make really cost at 50,000 operations a month?

Roughly $40-50/mo on a scaled Core tier, but this is slider-priced and not flat-published — confirm on the live make.com/pricing slider before committing. By contrast, n8n self-host runs ~$5-12/mo VPS for unmetered executions at that volume.

Can self-hosted n8n really replace Make or Zapier?

For execution cost, yes — the Community Edition is free software with unmetered executions; you pay only for a $3-18/mo VPS. The trade-off is ~1-3 maintenance hours a month plus DevOps responsibility, and it's source-available rather than OSI open source. If you don't want to run a server, n8n Cloud gives the same per-execution billing managed for you.