Compare n8n pricing with Zapier and Make by pricing the same workload, then adding hosting, maintenance and model usage.
n8n charges per workflow execution, Zapier per task and Make per credit, so the same automation can cost very different amounts on each. For an agency, I would price the same monthly workload on all three, then add model usage, hosting and maintenance time. The list prices below come from each vendor’s official pricing page.
Key takeaways:
- n8n counts one execution per workflow run, however many steps it has.
- Zapier counts each successful action step as a task; triggers, Filter, Paths and Formatter steps do not count.
- Make bills in credits, and most module actions use one credit.
- Self-hosted n8n has no license fee, but internal business use is the permitted case, and reselling it as a service needs a commercial agreement.
- Self-hosting adds updates, backups, monitoring and recovery work.
- Stay on a platform that works when switching costs more than it saves.
How does n8n pricing work?
n8n Cloud is priced by monthly workflow executions. On the n8n pricing page, Starter is 20 euros a month billed annually and includes 2,500 executions. Pro is 50 euros a month billed annually and includes 10,000 executions. Business is 667 euros a month billed annually and includes 40,000 executions, and the page lists it as a self-hosted plan. Enterprise is by quote. The page shows annual-billing prices only and says annual billing saves 17%.
n8n defines an execution as one full run of a workflow, regardless of how many steps it contains. That makes a long workflow cheap to run on n8n compared with a per-step meter. The page also says companies with fewer than 20 employees may qualify for 50% off Business through its startup plan.
When reviewing n8n pricing for an agency, also check who needs access and how client work is separated. A plan that suits one internal automation may not meet the permissions, support or licensing needs of a managed client service. Keep the quote with its date, billing basis and plan in your project notes, because a number without those is hard to compare later.
n8n pricing vs Zapier and Make: billing units
For a fair n8n pricing comparison, start with billing units. The three platforms count different things, and a workflow with many steps behaves differently on each.
Zapier counts a task each time a Zap successfully completes an action. Its Zapier pricing page says triggers do not count, and neither do Filter, Paths, Formatter, Delay, Looping, Sub-Zap or Storage steps. Make bills in credits: its Make pricing page says every time a module performs an action it consumes credits, that most actions consume 1 credit, and that the Router and error handler modules use none.
Pricing checked on 30 October 2026, from the official pages:
| Platform | Plan | Price listed | Included usage | Billing unit |
|---|---|---|---|---|
| n8n Cloud | Starter | 20 euros a month, billed annually | 2,500 executions | Workflow execution (one full run) |
| n8n Cloud | Pro | 50 euros a month, billed annually | 10,000 executions | Workflow execution |
| n8n | Business | 667 euros a month, billed annually | 40,000 executions | Workflow execution |
| n8n | Community Edition | No license fee (self-hosted) | Your own server limits | Not metered |
| Zapier | Free | $0 | 100 tasks a month | Task (successful action step) |
| Zapier | Professional | Starting from $19.99 a month on monthly billing | Depends on the task tier you select, from 100 up to 2M | Task |
| Zapier | Team | Starting from $69 a month on monthly billing | Depends on the task tier you select | Task |
| Make | Free | $0 | 1,000 credits a month | Credit (most actions cost 1) |
| Make | Core, Pro, Teams | See current pricing page | Depends on the credit volume you select | Credit |
Zapier states that yearly billing saves 33%, but its page does not show a per-month annual price for Professional or Team without choosing a task tier, so I have not quoted one. Make’s page also does not print plan prices without a credit selection, so use its calculator for your volume. Make’s page notes that credits replaced operations as the billing unit, so older articles that talk about operations may be out of date.

Is n8n free, and what does its license allow?
The n8n Community Edition is free to self-host, but under a specific license, not an unrestricted one. The Sustainable Use License says you may use or modify the software “only for your own internal business purposes or for non-commercial or personal use.” In practice, running n8n for your own agency’s internal automations is allowed. Reselling n8n as a service, or hosting it so clients can build and run their own workflows, needs a commercial agreement with n8n. Read the license and the official license FAQ against your intended architecture.
The FAQ distinguishes building and operating workflows from letting external customers build or configure workflow logic. It describes consulting and setup services as permitted examples while placing limits on offering workflow-building access as a service.
For an agency, that distinction deserves attention before designing a shared client portal. Calling the portal something else or hiding the original interface does not by itself resolve the licensing question.
The FAQ also describes circumstances where customers connect their accounts to prebuilt automations. Check the exact current explanation and seek confirmation from n8n when your proposed use is unclear; do not rely on a remembered summary of an older FAQ.
Free-to-use community software also has operating costs. Somebody still pays for infrastructure and time, owns the backup and responds when a credential expires or a workflow fails.
My one to one consultancy on tool choice can define the architecture and questions to resolve. A custom licensing decision should be confirmed with the vendor before implementation, rather than discovered after a client has been promised access.
n8n pricing: a worked cost comparison
This model is illustrative. It uses one made-up workflow and only the published billing units, with simple arithmetic. It is not a measured client workload.
Assume one workflow with a trigger and five action steps, all of which succeed, running 2,000 times a month.
- n8n: one execution per run, so 2,000 executions a month. That fits inside the 2,500 executions listed for Starter.
- Zapier: the trigger does not count, and each of the five actions counts as a task, so 5 x 2,000 = 10,000 tasks a month. You would pick a task tier that covers that volume and read its price on the pricing page.
- Make: five action modules at one credit each is 5 x 2,000 = 10,000 credits a month, plus whatever the trigger module consumes under Make’s rules. Check the price for that credit volume on the pricing page.
Now scale the same workflow to 10,000 runs a month. n8n counts 10,000 executions, which is the Pro allowance. Zapier would count up to 50,000 tasks and Make up to 50,000 credits. The gap grows with the number of steps, which is why step count matters more than the headline subscription price.
A complete n8n pricing estimate includes costs outside the platform meter: model usage for any AI step, paid integrations, retries, and the time to maintain the workflow. A subscription price on its own does not tell you what the automation costs.

Self-hosted n8n pricing and operating costs
Self-hosting means your team operates the software and infrastructure. Its monthly cost includes the server, storage, backups, monitoring, maintenance time and the consequences of a failed workflow, not merely a virtual-machine price.
Use a complete formula: infrastructure plus backups and storage, plus monitoring, plus maintenance hours multiplied by your internal hourly cost, plus any paid software or external usage. Keep one-off migration work separate so the recurring cost remains visible.
I do not quote a server price here because it depends on the provider, region, memory, storage, transfer and backup choices. Get a current quote from your host for the specification you need.
Capacity should follow the workload and reliability requirements. A tiny instance suitable for a personal experiment is not automatically an appropriate host for client-critical workflows with model calls and concurrent execution.
Budget time for updates, credential rotation, restore tests and incident investigation. Store the encryption and recovery material through an appropriate protected process, because a database backup alone may not be enough to recover credentials and a working service.
Before upgrading a self-hosted n8n instance, read the migration guidance for your installed version and your target version in the n8n documentation. Test the upgrade on a restored copy with external side effects switched off, then run your important workflows before touching production.
Keep the test results with the upgrade record so the next maintainer can repeat the checks.
I am Top Rated on Upwork with 100% Job Success. That is part of my delivery background, not evidence that self-hosting will save your agency money; the decision still needs a costed operating plan and a named owner.
When should you stay on Zapier or choose Make instead?
Stay with a platform when it already meets the requirement and the verified benefit of switching is too small. A migration should solve an observed cost, capability or ownership problem, rather than follow a tool comparison that ignores the existing system’s reliability.
Compare switching costs before migrating
My first rule is to check low-volume economics. If usage is small, the time spent rebuilding and operating a replacement can outweigh a subscription difference.
Second, do not self-host without an owner for patching, backups and recovery. “The developer will look at it” is incomplete if that person has no support agreement or availability commitment.
Third, respect uptime requirements. A business-critical workflow needs monitoring and a tested response path regardless of platform, and a managed service may fit the available team better.
Fourth, test the integrations you actually need. If the current platform handles an application well and the replacement requires a brittle custom connector, include that maintenance work in the comparison.
Fifth, count switching costs and business risk. A missed order notification, duplicated CRM record or delayed fulfillment action has an operational consequence even if the new monthly bill is lower.
Make may be a better fit when its scenario-building approach and supported integrations suit the workflow and the price for your credit volume suits. Test the actual branches and record handling before declaring it cheaper based on an entry plan.
For AI workflows, compare model and tool behavior separately from the orchestration platform. My AI agent development work includes that distinction because an expensive or unreliable prompt loop will not become economical simply by moving it. For an example of an AI workflow with strict limits, see How to Design an n8n AI Agent for Your WooCommerce Store.
How do you migrate from Zapier to n8n?
Migrate one observable workflow at a time, with a clear source of truth and a controlled handover. “Run in parallel” should mean compare outputs safely, not allow both platforms to send customer messages or create orders twice.
- Inventory the existing Zaps, owners, credentials, triggers and downstream actions. Identify which workflows are still needed.
- Rank them by verified cost, business importance and failure consequences. Choose a contained workflow for the pilot.
- Write the expected inputs, outputs and exception cases. Record the current behavior before rebuilding it.
- Rebuild one workflow using the target platform’s supported nodes and credentials. Check rate limits, pagination and data mapping explicitly.
- Replay safe fixtures and compare outputs in a test destination. Keep live side effects disabled on the new path during parallel evaluation.
- Test retries and duplicate prevention. A repeated event should not create an unintended second business action.
- Agree a cutover window and disable the old live path before enabling the replacement’s side effects. Keep a rollback plan and event reconciliation notes.
- Monitor the first complete operating cycle, then retire unused credentials and document ownership. Do not delete the old configuration before the recovery decision is clear.
Filters, loops, scheduling and error behavior do not necessarily map one to one. My business automation service starts with those differences and the current cost evidence before deciding what is worth moving.
My automation services also cover the handover: who maintains the system, what alerts mean and how the owner can stop it. That responsibility belongs in the comparison alongside the platform bill.
Frequently asked questions
How much does n8n cost?
On n8n’s cloud plans, Starter is listed at 20 euros a month billed annually for 2,500 executions, and Pro at 50 euros a month billed annually for 10,000 executions. Business is listed at 667 euros a month billed annually for 40,000 executions, and Enterprise is by quote. n8n charges per workflow execution, not per step. The self-hosted Community Edition has no license fee, but you pay for hosting and maintenance. Prices checked on 30 October 2026, so confirm them on the pricing page.
Is n8n cheaper than Zapier?
It depends on how many steps your workflows have. n8n counts one execution per workflow run, while Zapier counts each successful action step as a task. A five-step workflow running 2,000 times is 2,000 executions on n8n and up to 10,000 tasks on Zapier. Zapier’s prices depend on the task tier you pick, so compare your own volume on both pricing pages.
Is self-hosted n8n free?
The Community Edition has no license fee, and the Sustainable Use License allows use for your own internal business purposes. Reselling n8n as a service, or giving clients access to build workflows on your instance, needs a commercial agreement with n8n. Hosting, backups, updates and support still cost money and time.
When should I stay on Zapier?
Stay when your workflows are reliable, usage is modest, the integrations you need work well and the saving from switching does not cover migration and operating costs. Also consider your team’s support capacity and uptime needs.
How hard is migrating from Zapier to n8n?
The effort depends on triggers, data mapping, integrations, error handling and side effects. Inventory the existing workflow, rebuild one contained case and compare safe test outputs before cutover. Prevent duplicate live actions during parallel running, keep a rollback route and document who owns the replacement after launch.
If you are weighing n8n against Zapier or Make for your agency or store, my business automation service starts with a cost and risk review of your current workflows, then rebuilds the ones worth moving.




