You built a few Zaps. Things were working. Then you clicked over to the Zapier pricing page to upgrade, saw that your workflow would run about $299 a month at your current volume, and immediately opened a new tab to Google "Zapier alternatives." That moment of sticker shock has probably sent more people to Make and n8n than any marketing campaign those platforms ever ran.
Here's the honest answer before we get into the details: n8n is for developers and self-hosters who want no ceiling on their costs, Make is for visual builders who want Zapier's power at a fraction of the price, and Zapier is for non-technical teams who need it to just work without anyone touching a server. The rest of this post is just the math and nuance behind that sentence.
First, What Even Is an "Operation"?
Every platform has its own word for the unit of work they bill you on, and they are not the same thing — which makes price comparisons genuinely annoying.
- Zapier calls them Tasks. A task is each action step that runs successfully. The trigger doesn't count. So a 3-step Zap (trigger → action → action) costs 2 tasks per run.
- Make calls them Operations. Every module execution counts — including the watch/trigger module in many scenarios. A 3-module Make scenario can cost 3 operations per run.
- n8n calls them Executions (on cloud) or just runs (self-hosted). Cloud plans count each workflow execution regardless of how many nodes fire inside it. Self-hosted has no billing unit at all — you just run your server.
Why does this matter? Because a "10,000 operations" plan on Make and a "10,000 tasks" plan on Zapier are not equivalent. Depending on your workflow complexity, you might get significantly more mileage out of one versus the other. Always model your specific workflow before comparing sticker prices.
The Real Cost Comparison Table
Let's cut straight to the numbers. These are based on published pricing as of May 2026. "Operations" here means equivalent workflow steps executed — adjusted for how each platform counts them.
| Monthly Volume | Zapier | Make | n8n Cloud | n8n Self-Hosted |
|---|---|---|---|---|
| 10,000 ops | $29/mo (Starter) | $9/mo (Core) | $20/mo (Starter) | ~$6/mo (VPS) |
| 50,000 ops | $73/mo (Professional) | $16/mo (Core) | $20–$50/mo | ~$6/mo (VPS) |
| 100,000 ops | $149/mo (Professional) | $29/mo (Pro) | $50/mo (Pro) | ~$12/mo (VPS) |
| 500,000 ops | $299–$599/mo (Team) | $59–$99/mo (Teams) | Custom/Enterprise | ~$20/mo (VPS) |
The 100,000 ops row is highlighted because that's roughly the inflection point where the cost gap becomes hard to ignore. At that volume, Make is running 5× cheaper than Zapier, and self-hosted n8n is running 12× cheaper. If you're anywhere near that number and still on Zapier, the sticker shock you felt on the pricing page is valid.
Automation platform pricing changes frequently and varies by billing cycle (monthly vs. annual). Annual billing typically saves 20–40% across all three platforms. The figures above use monthly billing and mid-tier plans; your actual cost depends on workflow complexity, team seats, and feature requirements. Use our cost comparison calculator to model your specific volume.
Hidden Costs Nobody Talks About
The advertised price and the real price have a way of diverging once you're actually using these tools at volume. Here are the billing traps that catch people off guard on each platform.
Zapier: Multi-step task counting adds up fast
Zapier's task counting model means that workflows with lots of steps are proportionally more expensive than simple ones. A lead enrichment workflow that hits 5 action steps (filter, lookup, enrich, update CRM, send Slack message) costs 4 tasks every time it fires — not 1. At 5,000 leads per month, that's 20,000 tasks just from one workflow. Teams building moderately complex automation stacks often burn through their task quota 3–4× faster than they estimated.
Zapier also pauses Zaps (rather than charging overages) when you hit your limit, which sounds friendly until your time-sensitive automations silently stop running mid-month. (Yes, that happens. No, they don't re-run retroactively.)
Make: Data operations vs. task operations
Make's operation counting is generally favorable, but there's a subtlety in multi-route scenarios. If your scenario has conditional branches (routers), each active route's modules count separately. A scenario with 3 routes, each with 3 modules, can burn 9 operations per run even if most of the logic is just routing. Complex scenarios with error handlers, iterators, and aggregators need careful planning.
Make also restricts the minimum update interval by plan tier — the free plan runs every 15 minutes, Core every 5 minutes, and real-time triggers require higher tiers. If your business needs instant responses to events, factor that into your plan selection.
n8n Cloud: Execution-based pricing is deceptively cheap
n8n Cloud counts executions per workflow run, not per node. That's actually quite favorable compared to Zapier and Make for complex workflows. The catch is that n8n Cloud's lower tiers have monthly execution limits that can feel tight if you have high-frequency polling workflows. A workflow that checks an API every minute generates 43,200 executions per month on its own.
The Self-Hosting Math: When Does n8n Actually Win?
The self-hosted n8n story sounds almost too good — free software, run as many workflows as you want, pay only for the server. Let's sanity-check that against real numbers.
A typical n8n self-hosted setup runs comfortably on a $6/month VPS from Hetzner or a $12/month droplet on DigitalOcean. That covers most small-to-medium automation loads. For heavier workflows or teams that need high availability, budget $20–$40/month for a beefier instance or a managed Postgres database.
The honest caveat: self-hosting costs developer time. Initial setup is 1–3 hours for someone reasonably comfortable with Docker. Ongoing maintenance is maybe 30 minutes a month for updates. If your time is worth more than about $40/hour, the math gets murkier below the Zapier Starter plan level. But once you're above $50/month on Zapier, self-hosted n8n pays for itself in time savings pretty quickly.
One more wrinkle: n8n self-hosted runs on your infrastructure, which means uptime and reliability are your responsibility. If a workflow fails at 2am and your server is the reason, nobody's sending you a status page notification. For mission-critical automation, you either need solid DevOps practices or you pay the managed cloud premium — which is what Make and Zapier are actually selling you.
Who Should Pick Which
The platform choice is less about features and more about what kind of organization you are.
Pick Zapier if...
- Your team has no developers and no one who wants to touch a server
- You need the widest possible app library — Zapier's 6,000+ integrations is genuinely unmatched
- You're a small team running under 10,000 tasks/month and the $29 Starter plan fits
- Reliability and support SLAs matter more than saving $100/month
Pick Make if...
- You want Zapier's visual builder experience at 3–5× lower cost
- Your workflows are moderately complex — Make's visual scenario builder handles branching and data transformation better than Zapier out of the box
- You're comfortable with a small learning curve (Make's interface is slightly more technical than Zapier's)
- You're a freelancer or agency building automations for clients — Make's pricing scales much better
Pick n8n if...
- You have at least one developer on the team, or you're one yourself
- Your automation volume is high enough that per-operation pricing starts to hurt
- You want to write custom JavaScript nodes for logic that no built-in integration handles
- You're building internal tools where the data stays on your own infrastructure (HIPAA, GDPR, or just paranoia about your data living in someone else's cloud)
A Few Things That Don't Show Up in the Price Comparison
App library depth: Zapier wins. Make has solid coverage of 1,500+ apps but still has gaps. n8n's library is the smallest of the three, though you can fill gaps with HTTP request nodes and custom code — which requires knowing what you're doing.
Error handling: Make has the most mature built-in error handling with scenario error routes. n8n gives you full control via code but requires more setup. Zapier's error handling is simple and decent for straightforward workflows.
AI-native workflows: All three platforms now support AI agent nodes and LLM integrations. n8n has arguably the most flexible implementation (you can wire up any model or custom endpoint), while Zapier's AI features are more polished for non-technical users. Make is in the middle.
Team collaboration: Zapier and Make both have solid multi-user workspace features on paid plans. n8n self-hosted requires you to manage user access yourself — fine for a small team, more work at scale.
Frequently Asked Questions
Is n8n really free?
n8n is free to self-host — the community edition has no operation limits, no workflow limits, and no expiration. You pay for the server you run it on (typically $5–$20/month on a VPS) and your own time to set it up. The cloud-hosted n8n.io plans start at $20/month and do have execution limits. So: free to self-host, not free on their managed cloud.
Can Make replace Zapier?
For most use cases, yes. Make (formerly Integromat) supports the same kinds of app connections as Zapier — it just calls them scenarios instead of Zaps, and charges per operation rather than per task. Make is meaningfully cheaper at mid-volume (10K–100K ops/month) and has more powerful data-manipulation features. The tradeoff is a steeper learning curve and a slightly smaller app library.
Is n8n hard to self-host?
Not particularly hard, but it requires comfort with the command line. The easiest path is a one-click deploy on Railway, Render, or Elestio — takes about 15–30 minutes. Running it on a VPS (DigitalOcean, Hetzner, AWS) requires Docker and a reverse proxy like nginx or Caddy, which adds another hour or two if you haven't done it before. Once it's running, day-to-day management is minimal.
What happens when you exceed Zapier's task limit?
Zapier pauses your Zaps — they stop running until the next billing cycle starts. You won't be charged overages automatically; instead, your automations just quietly break. You can upgrade your plan mid-cycle to unblock them, but the paused tasks don't re-run retroactively. This makes it critical to monitor your task usage if your workflows handle time-sensitive data.
What's the difference between Zapier tasks and Make operations?
Zapier counts a "task" as each action step that successfully runs in a Zap — the trigger doesn't count, but every subsequent step does. Make counts "operations" similarly, but each module execution (including the trigger/watch step in some scenarios) counts. A 3-step Zapier Zap uses 2 tasks per run; a similar Make scenario might use 3 operations. Always map your specific workflow against each platform's counting rules before comparing plans.
Which is better for large-scale automation — n8n or Make?
For very high volumes (500K+ operations/month), self-hosted n8n is almost always the cheapest option — you're paying for server costs, not per-execution fees. Make's enterprise plans are available but get expensive at scale. Zapier's volume tiers can run into thousands of dollars per month. If you have the technical capacity to self-host, n8n wins on cost at high volume by a wide margin.
Does Make.com have a free plan?
Yes. Make's free plan includes 1,000 operations per month, two active scenarios, and a 15-minute minimum update interval. It's enough for simple personal automations but not for anything business-critical. The Core paid plan starts at $9/month for 10,000 operations with 5-minute intervals, which is where it becomes genuinely useful.
The answer you're probably looking for isn't "which platform is objectively best" — it's "which platform is best for the volume and team I have right now." Plug in your actual monthly run counts and step complexity, and the cost difference usually makes the decision for you.