n8n vs Zapier comes down to who will maintain the automation and how many steps each run has. If a developer or a technical owner will keep it running and your workflows are long, n8n is usually the better fit. If the job is a short handoff between two apps and a non-technical person will own it, Zapier is usually quicker and simpler.
We build client automations in both, and we lean toward n8n for new custom work. This post covers how each one bills, where Zapier is the right call, and what to check before you choose. If you want a second opinion on your own stack, our n8n build work is where we do most of this.
How n8n and Zapier bill, as of November 3, 2026
Prices and limits go stale fastest, so they all sit in this section. We read them off zapier.com/pricing and n8n.io/pricing on November 3, 2026. Re-check both before you decide.
| Item | Zapier | n8n Cloud |
|---|---|---|
| Billing unit | Task: a successfully completed unit of work | Execution: one run of the whole workflow |
| What does not count | Failed actions, triggers, polling, built-in tools like Filter, Formatter and Paths | Step count and data volume do not change the count |
| Free or entry tier | Free: 100 tasks a month, two-step Zaps only | Starter: 2.5K executions a month, listed at 20 EUR a month billed annually |
| Next tier up | Pro: 750 tasks from $19.99 a month billed annually, $29.99 billed monthly | Pro: 10K executions, listed at 50 EUR a month billed annually |
| Going over | Pay-per-task bills extra tasks at a higher rate, or usage stops at your limit | Overage fees are capped on Starter and Pro |
| Self-hosting | Not on the pricing page | Self-hosted Community Edition available |
Two details change the math. Zapier says self-serve task allowances reset monthly, even on annual plans, and it lists AI steps and some other actions as costing more than one task. n8n lists the Business plan as self-hosted only, with Cloud on a waitlist. Both vendors publish more tiers than we show here, so use the pricing pages for the full list.
A worked cost example
Take a lead-intake workflow with a webhook trigger and six action steps: look up the contact, enrich the company, score it, write the CRM record, post to Slack and send a confirmation email. Say it runs 200 times a month.
On Zapier, the trigger is free and each of the six actions is listed at one task, so that is about 1,200 tasks a month, assuming no AI step and no failed runs. That is past the 750-task Pro tier, so you would be looking at the 1,500-task tier, listed at $39.00 a month billed annually or $58.50 billed monthly.
On n8n Cloud, the same workflow is 200 executions, well inside the Starter plan's 2.5K. Add a second and third workflow of similar size and you are still counting runs, not steps.
A short Zap goes the other way. A single Zap that copies new form entries into a sheet is one trigger and one action. At 100 runs a month that sits right on the Zapier free plan limit, and nobody needs to learn a new tool to maintain it. We would not move that to n8n.
Where n8n wins
Long workflows cost less. Because n8n counts the run instead of the steps, adding a step to a workflow costs nothing extra on Cloud, so we branch, retry and add a cleanup step without checking a task meter first.
Custom logic is also easier. We use the Code node, the HTTP Request node and webhooks constantly. The MCP setup we use to drive n8n from Claude Code is written up in our n8n MCP server guide.
Self-hosting keeps data on a server you control, which some clients need for a contract reason. Skip this one if nobody has asked you for it.
Where Zapier wins
A first working version arrives sooner. For common app pairs, a person with no technical background can have a Zap running in an afternoon, and you rarely have to hand-write an API call.
If the person who maintains the automation is an office manager, not a developer, a tool they can read and edit without help is worth more than a lower bill. A workflow nobody on the client side dares to touch is a design failure on our end, and a Zap would have avoided it.
With Zapier nobody patches a server or updates a container. n8n Cloud removes most of that work too, but self-hosted n8n does not.
What we'd do
Count steps per run before you compare prices. If most of your automations are two or three steps and a non-technical person owns them, stay on Zapier and watch the task meter. If you have workflows with six or more steps, branching, code or an AI step, price them on n8n Cloud first, and consider self-hosting only if you have someone who will keep the server patched.
If you are choosing between n8n and Make as well, we compared those in n8n vs Make, and the n8n side of the bill is broken down in n8n pricing explained.
For a look at what a multi-step build contains, one of our recorded runs shows a Stripe deposit becoming a deal update, a project plan and a kickoff doc. Jobs with that many steps are where per-execution billing and per-task billing diverge.
Mistakes to avoid when you switch
Do not migrate everything at once. Move the workflow that is closest to hitting your Zapier limit first, run it beside the Zap for a week, and compare outputs row by row. Duplicate sends are the usual failure, so turn the old Zap off the moment the outputs match.
Do not assume your counts carry over. Zapier does not bill triggers or polling, but an n8n schedule that runs every five minutes is about 8,600 to 8,900 executions a month by n8n's own pricing page. Frequent schedules can eat an execution allowance fast, so check how often a trigger really fires.
Do not skip error handling. Zapier does not count failed actions toward tasks, which makes a broken Zap cheap but easy to miss. In n8n, set an error workflow so a failure pings someone instead of waiting until a client asks where their email went.
If you want this set up on your stack, grab a time and we'll look at your current Zaps, count the steps, and tell you what we'd move. Our n8n automation services page covers how we scope it.
Frequently asked questions
- Is n8n better than Zapier?
- For long, branching or code-heavy workflows we pick n8n, and for a short two-app handoff that a non-technical person will own, Zapier is often the faster and safer choice. Neither wins in the abstract. The deciding factors are step count per run, who maintains the automation, and whether you want the option to self-host.
- Is Zapier vs n8n cheaper for a small business?
- It depends on workflow length and volume. As of November 3, 2026, Zapier bills per successful task, which means per action step, while n8n Cloud bills per execution, which is one run of the whole workflow. Long workflows that run often tend to cost less on n8n, and a handful of short Zaps can be cheaper or free on Zapier. Check both pricing pages for current figures.
- Can I self-host Zapier like I can with n8n?
- We did not find a self-hosted Zapier option on its pricing page. n8n offers a self-hosted Community Edition you run on your own server, with installation docs linked from its pricing page. If hosting on your own infrastructure matters to you, confirm Zapier's current options with Zapier directly.
- Is Zapier easier to learn than n8n?
- Most non-developers find Zapier easier to start with, and n8n gets comfortable once you understand JSON and expressions. That is our experience building client work in both, not a measured result. If a non-technical person on your team will edit the automation, have them try both free options first.
- How hard is it to move from Zapier to n8n?
- You rebuild the logic instead of importing it, so the effort scales with the number of Zaps and how much custom logic each one has. The safe path is to run the new n8n workflow side by side with the old Zap on real data, compare outputs, then switch over and turn the Zap off.