Zapier vs Make vs n8n: Tasks, Credits and Executions, Priced Honestly
Automation tools all sell "a monthly allowance of work," but each counts the work differently — Zapier per task, Make per credit, n8n per execution — so the headline prices ($19.99, $9, €20) are not comparable until you run the same workflow through all three models. We did. The gap is not small: a modest five-step workflow can cost roughly ten times more on one platform than another.
At a glance
| Zapier | Make | n8n | |
|---|---|---|---|
| Billing unit | Task = each successful action step (trigger free) | Credit = each module run (renamed from "operations" in Jan 2026) | Execution = one full workflow run, any length |
| Free plan | 100 tasks/mo, two-step Zaps only | 1,000 credits/mo, 2 active scenarios | Self-hosted Community Edition: free, unlimited |
| Entry paid plan | Professional $19.99/mo (annual) — 750 tasks | Core $9/mo (annual) — 10,000 credits | Cloud Starter €20/mo — 2,500 executions |
| App directory | 9,000+ apps | 3,500+ apps | 400+ native, plus HTTP/webhooks for anything else |
| Watch out for | Every step bills; volume gets expensive fast | Polling triggers burn credits even when idle | Self-hosting is your job: updates, security, uptime |
The same workflow, three bills
Take a typical small-team workflow: a five-step lead router (trigger + four actions) running 2,000 times a month.
| Units consumed / month | Plan needed | Monthly cost (annual billing) | |
|---|---|---|---|
| Zapier | 4 tasks × 2,000 = 8,000 tasks | Professional, 10,000-task tier | ~$129 |
| Make | ~5 credits × 2,000 = 10,000 credits | Core | $9 |
| n8n | 2,000 executions | Cloud Starter — or self-hosted | €20 (or ~$0 self-hosted) |
Even at gentle volumes the shape holds: 5,000 simple two-step automations a month cost about $9 on Make Core versus roughly $89 on Zapier's 5,000-task tier. Zapier's defense is real — setup is faster, the app directory is unmatched, and its built-in tools (filters, paths, formatter) do not consume tasks — but you are paying for convenience per unit of work, forever.
Where the bill hides
Make's polling trap
Since Make renamed operations to credits in January 2026, a polling trigger consumes one credit on every check, even when it finds nothing new. A scenario polling every minute burns about 43,200 credits a month — more than four times the entire Core allowance — before it has automated anything. Zapier, by contrast, never charges for an empty poll. On Make, set polling intervals deliberately (15 minutes is usually plenty) or use webhooks.
Zapier's step multiplication
Every action step in a Zap is a separate task, and paths/filters count as steps too. A "simple" 7-step Zap run 1,000 times is 7,000 tasks. Teams routinely discover this on their second invoice. Model your highest-volume Zap before choosing a tier.
n8n's real price is your time
Self-hosted n8n is free and unlimited, and for developers already running a VPS it is close to unbeatable. But you own updates, backups, credentials security and uptime. The €20/mo Cloud Starter (2,500 executions) is the honest comparison point if you would rather not. Note also that n8n bills in euros.
Which one should you pick?
- Pick Make if you want the most automation per dollar, your workflows branch or loop, and you will keep an eye on polling intervals. Best default for solo developers and small remote teams.
- Pick Zapier if a must-have app is only integrated there, non-technical teammates will build their own Zaps, or your volume is low enough that the per-task premium stays small.
- Pick n8n if you are a developer with long, complex workflows — especially AI-agent pipelines — and either self-hosting is trivial for you or per-execution cloud billing fits your shape of work.
Links above are affiliate links (see disclosure). Pricing confirmed on the vendors' sites as of November 2026.