All Guides

n8n, Zapier or Make: paying per step or per run

Zapier and Make count every action, n8n counts the whole workflow run. Three worked examples without prices show how far the counting methods drift apart.

Dirk Hesse
November 18, 2026
17 min read

You automate tasks with Zapier, Make or n8n and want to know what it costs at higher volume? The answer depends heavily on what the provider counts. Zapier counts tasks, Make counts module runs and bills them in credits, n8n Cloud counts executions of a whole workflow (sources: Zapier Help, Make Help, n8n pricing, as of Nov 11, 2026). If you self-host n8n, you mainly pay for the server and your own time to run it.

This article lists no prices. Plans and amounts change, and the pricing pages of all three providers are linked. Instead, we calculate with the counting rules the providers document themselves and use three workflow profiles to show how far the counted units drift apart. With these numbers you go to the pricing pages and look for the plan whose quota fits.

Server prices for your own n8n instance are in the n8n calculator and the VPS comparison. How to set up n8n on a VPS is covered in the n8n self-hosting guide.

Note on compensation: RackDiff receives a commission from some providers when you book via labelled links, including the offer buttons in this article; your price does not change. How we sort and weight offers is explained in our methodology.

TL;DR - Quick answer

  • Zapier counts every successful action as a task; triggers, filters and formatters do not count (per Zapier Help, as of Nov 11, 2026).
  • Make counts every module run as an operation, one operation per check for the trigger (per Make Help, as of Nov 11, 2026), and bills in credits; an ordinary action uses one credit (per Make pricing, as of Nov 11, 2026).
  • n8n Cloud counts executions: one run of the whole workflow is one execution, no matter how many steps it has (per n8n pricing, as of Nov 11, 2026).
  • Self-hosted n8n runs as the Community Edition without a licence key (per n8n docs, as of Nov 11, 2026), with no licence fee. You pay for server, domain and operations; compare servers in the n8n calculator.
  • Key point: The more actions a workflow has, the further the counts drift apart. With one trigger and four actions, Zapier counts four units per run, Make five and n8n Cloud one. Whether that costs less depends on plan, quota and price per unit.

How do Zapier, Make and n8n bill?

The three cloud services count different units, and the unit helps decide which plan fits your workflow. The table below sums up the billing unit; amounts and quotas per plan are on the linked pricing pages.

ServiceBilling unitWhat differs per plan
ZapierTask per successful action (per Zapier Help, as of Nov 11, 2026)Feature set and task quota; multi-step Zaps from Professional (per Zapier pricing, as of Nov 11, 2026)
MakeCredits for module runs (per Make pricing, as of Nov 11, 2026)Credit quota; extra credits in bundles (per Make pricing, as of Nov 11, 2026)
n8n CloudExecution per workflow run (per n8n pricing, as of Nov 11, 2026)Executions per month and concurrent executions (per n8n pricing, as of Nov 11, 2026)
Self-hosted n8nno licence fee without a licence key (per n8n docs, as of Nov 11, 2026)Server resources you choose yourself

At Zapier, the plan sets the feature set and the task quota. Many actions use more than one task; how many depends on the step type, the AI model tier and the number of tool calls (per Zapier pricing, as of Nov 11, 2026). A successful ordinary action step counts one task per run (per Zapier Help, as of Nov 11, 2026).

Make bills in credits. Every action in a scenario uses credits; an ordinary action uses one, features via Make's AI Provider can use more (per Make pricing, as of Nov 11, 2026). For standard modules, credits therefore equal operations. Credits in a subscription expire at the end of the term (per Make pricing, as of Nov 11, 2026).

n8n bills by monthly workflow executions; how complex a workflow is plays no role. The cloud plans are called Starter, Pro and Enterprise; Business is currently self-hosted only. The plans differ in execution quota and concurrent executions, among other things; n8n caps neither users nor workflows in any plan (per n8n pricing, as of Nov 11, 2026).

Without a licence key, self-hosted n8n runs as the Community Edition; Business and Enterprise need a licence key (per n8n docs, as of Nov 11, 2026). Both plans are also billed by production executions, summed across all instances with the same key (per n8n pricing, as of Nov 11, 2026).

What counts as a task, an operation or an execution?

The three terms sound alike but measure different things. A task and an operation measure single steps of a workflow, an execution measures the whole run. That creates the gap you see in your usage.

Zapier: task

A task is a successfully executed action; failed actions do not count. Triggers, polling and testing an action use no tasks, and neither do Filter, Paths, Formatter and Delay (per Zapier Help, as of Nov 11, 2026). A Zap with one trigger and four ordinary actions therefore uses four tasks per successful run.

From December 1, 2026, Next Gen Zaps also use tasks, at the same rates as Classic Zaps and with at least one task per completed run; Classic Zaps keep running unchanged (per Zapier Help, as of Nov 11, 2026).

Make: operation and credit

An operation is a single module run. A trigger module uses one operation per check; the following modules run once per data packet (bundle), so ten times for ten bundles (per Make Help, as of Nov 11, 2026). Router and error handler modules use no credits (per Make pricing, as of Nov 11, 2026).

A scenario with one trigger and four actions that processes one bundle per run therefore counts five operations per run. If the trigger fetches ten new records at once, the four actions run ten times each, and by this rule the run counts 41 operations (own calculation).

n8n: execution

An execution is one run of the whole workflow; how many steps it has and how much data it processes changes nothing about that (per n8n pricing, as of Nov 11, 2026). Only production runs count: a Schedule Trigger counts every time it fires, a polling trigger only when it finds new data, a webhook for every request that starts the workflow. Manual runs in the editor, sub-workflows (the parent run counts) and error workflows are not counted (per n8n docs, as of Nov 11, 2026).

How often the trigger checks

Own calculation: a trigger that looks for new data every 15 minutes checks 2,880 times in 30 days. Make counts one operation per check (per Make Help, as of Nov 11, 2026). At Zapier, polling checks use no tasks (per Zapier Help, as of Nov 11, 2026). At n8n, a polling trigger only counts checks with new data, a Schedule Trigger on the other hand counts every time it fires (per n8n docs, as of Nov 11, 2026). So look at how your workflow starts before you estimate the runs per month.

Worked example without prices: three workflow profiles

The three profiles are own calculations based on the counting rules per Zapier Help, Make Help and n8n's pricing page (as of Nov 11, 2026). Assumptions: every action uses exactly one task or credit (no AI steps, no filters or routers), every module processes one bundle per run, the Zap is a Classic Zap, and a month has 30 days. For Make, the trigger check is included once per run. The units carry a different price per provider and plan; which calculation costs you less only shows when you compare it with the current pricing pages. Plans and counting rules can change; the linked provider pages are what counts.

ProfileWorkflowRuns per monthZapier: tasksMake: operationsn8n: executions
HobbyTrigger and 2 actions, 10 runs a day300600900300
FreelancerTrigger and 4 actions, 100 runs a day3,00012,00015,0003,000
TeamTrigger and 9 actions, 1,000 runs a day30,000270,000300,00030,000

The formulas behind it are simple. Zapier counts actions times runs. Make counts actions plus trigger times runs. n8n Cloud counts only the runs. With two actions, Zapier and n8n Cloud differ by a factor of two, with nine actions by a factor of nine.

Hobby: A form posts a message to a chat and adds a row to a spreadsheet. At 300 runs a month, the difference in absolute numbers is small. What matters more here is whether the plan allows multi-step workflows; at Zapier that is the case from Professional (per Zapier pricing, as of Nov 11, 2026).

Freelancer: New orders are checked, sent to the CRM, linked to an invoice, confirmed by email and announced in a channel. 3,000 runs become 12,000 tasks at Zapier and 15,000 operations at Make. Compare these numbers with the quotas on the pricing pages; the quota you need grows with every extra action in the workflow.

Team: A workflow with nine actions that runs a thousand times a day produces six-figure numbers at the step-based services and 30,000 executions at n8n Cloud. At this size, your own n8n instance is also an option. n8n states an execution quota only for paid plans (per n8n docs, as of Nov 11, 2026); how many runs the Community Edition handles depends on your server.

From December 1, 2026, a Next Gen Zap also uses at least one task per completed run (per Zapier Help, as of Nov 11, 2026); this changes nothing in the table, because every run there has at least two actions. Count the actions of your own workflow and estimate the runs per month; then you compare the plans in the right units.

What happens when the quota runs out?

At Zapier, the pay-per-task setting decides. If it is on, Zaps keep running, and Zapier charges extra tasks at a separate rate, up to three times the quota. Without pay-per-task, Zapier holds further runs until the next billing period (per Zapier pricing, as of Nov 11, 2026).

At Make, scenarios only continue once credits are available again. Extra credits come in bundles, and in the Core, Pro and Teams plans also as automatic top-up (per Make pricing, as of Nov 11, 2026).

For n8n Cloud, the pricing page only shows "Capped" for Starter and Pro in the overage fees row, without an explanation. For self-hosted Business and Enterprise plans, workflows keep running when the quota is exceeded, but overage charges may apply (per n8n pricing, as of Nov 11, 2026). Clarify what happens in your plan before you book. On your own server, throughput depends on CPU, RAM and database.

What does n8n cost when you self-host it?

Self-hosted without a licence key, you pay no licence fee. Instead you pay for other items, and one of them is your time.

  • Server: To start, you need a VPS that runs Docker. How much RAM and CPU your setup needs is estimated by the n8n calculator; current prices are in the VPS comparison.
  • Database: n8n uses SQLite by default and supports PostgreSQL (per n8n docs, as of Nov 11, 2026). PostgreSQL is another service that you back up and update.
  • Scaling: In queue mode, a main instance receives the triggers and workers run the executions; you need Redis and a database for it, and the mode is not recommended with SQLite (per n8n docs, as of Nov 11, 2026). The Community Edition includes queue mode (per n8n docs, as of Nov 11, 2026).
  • Domain and HTTPS: For webhooks from outside you need a domain and a reverse proxy with a certificate. The n8n self-hosting guide shows the setup with Caddy.
  • Operations: You handle updates, backups and monitoring yourself. Plan fixed time for that every month.

Contabo offers n8n preinstalled on a VPS you choose when ordering; on existing VPS or VDS it can be installed via the Customer Control Panel. Provisioning with the n8n image can take up to 30 minutes (per Contabo website, as of Nov 11, 2026). Maintenance, updates and troubleshooting of the included open-source software are up to you; Contabo says it is not responsible for the licences of the software in the image (per Contabo website, as of Nov 11, 2026). The preinstallation shortens the start, not the operations. Whether your host offers an n8n image is on its website; for this article we only checked Contabo's offer. Details on the provider are on the Contabo page.

Mind the licence. The Sustainable Use License allows use and modification only for your own internal business purposes or for non-commercial or personal purposes; you may only pass the software on without charge and for non-commercial purposes (per n8n licence text, as of Nov 11, 2026). Whether your use falls under it, for example if you run n8n for clients, is governed by the licence text. This section is not legal advice; check the licence text if in doubt.

On data location: on your server, the data sits where you ordered the server, and you can choose the location. If you process other people's data, you remain responsible for complying with the GDPR, usually with a data processing agreement with the host. Background is in the article on VPS providers in Germany (German).

VPS for n8n: matching plans

The cheapest plans with at least 2 GB RAM, 1 vCPU and 20 GB storage, sorted by price. For n8n these are the defaults of our calculator.

Prices incl. VAT · Prices as of Nov 18, 2026 · How we rank (methodology)

Compare all 64 matching plans →

When does n8n Cloud pay off?

n8n Cloud is an option if you want to use n8n but do not want to look after your own server. Counting by executions stays the same even for long workflows, because the number of steps does not go into the quota. In the hosted plans, n8n stores the data in the EU, on servers in Frankfurt (per n8n pricing, as of Nov 11, 2026). If you process other people's data, you remain responsible for GDPR compliance here too.

When building a workflow, it helps that manual runs in the editor do not count (per n8n docs, as of Nov 11, 2026). You can start a workflow by hand as often as you like while developing it, without using up your quota.

The limits of n8n Cloud are the execution quota and the number of concurrent executions, which differs per plan (per n8n pricing, as of Nov 11, 2026). If your workflows produce many short runs, for example via webhooks, the number of executions rises fast even if every run has only a few steps. Then you compare the executions per month with the plan's quota and with the cost of your own server.

A mixed approach is possible: you start in the cloud and later move workflows with many runs to your own server. How the move works is described in the FAQ of the n8n self-hosting guide.

Conclusion

Zapier counts actions, Make counts modules, n8n Cloud counts runs, and self-hosted n8n without a licence key depends on your server. For small workflows with few actions, the numbers are close, and the choice depends more on integrations and ease of use. The more actions a workflow has and the more often it runs, the further the counted units drift apart. Whether that costs less depends on plan, quota and price per unit.

Do the maths for a workflow that runs often for you: actions times runs per month for Zapier, the same plus trigger for Make, just the runs for n8n Cloud. With these numbers you compare the quotas on the pricing pages. If your own server is an option, you find suitable sizes in the n8n calculator and the setup in the n8n self-hosting guide.


Frequently asked questions

What is an execution in n8n?
Per n8n, an execution is one run of the whole workflow, no matter how many steps it has. Only production runs started by a trigger, a schedule or polling count; manual runs in the editor and sub-workflows do not.
Do triggers count as tasks at Zapier?
No. Per Zapier, triggers use no tasks, and neither do Filter, Paths, Formatter and Delay. An ordinary successful action step counts one task, AI steps can use more.
Why does Make count more than Zapier for the same workflow?
Make counts every module run as an operation, one per check for the trigger. A workflow with one trigger and four actions counts five operations per run at Make and four tasks at Zapier. What that costs depends on the price per unit in each plan.
Are there licence fees for self-hosted n8n?
Without a licence key, n8n runs as the Community Edition with no licence fee; Business and Enterprise need a licence key. The Sustainable Use License allows use only for your own internal business purposes or for non-commercial or personal purposes; whether your use falls under it is governed by the licence text, and this answer is not legal advice. Costs arise for the server and operations.
Do manual trial runs count?
At Zapier, testing an action uses no tasks, per Zapier. At n8n, manual runs in the editor do not count as executions, per n8n.
Which server is enough for n8n?
That depends on the number of concurrent workflows, the amount of data and the database. The n8n calculator estimates your needs and shows suitable servers; how the list is weighted is explained on the methodology page.

Find a server for n8n

The calculator estimates what your n8n installation needs and shows suitable servers.

Open the n8n calculator

Next step: the cheapest plans for n8n

The cheapest plans with at least 2 GB RAM, 1 vCPU and 20 GB storage, sorted by price. For n8n these are the defaults of our calculator.

Prices incl. VAT · Prices as of Nov 18, 2026 · How we rank (methodology)

Compare all 64 matching plans →

Matching VPS Calculator

n8n selber hosten: Server, Kosten und Anforderungen 2026

Was n8n an RAM und CPU braucht, was der Betrieb kostet und worauf du beim Server mieten achtest

Go to Calculator

Related Articles