n8n vs Zapier vs Make: Which One Go Save You Money?

Difference wey dey decide everything

n8n, Zapier and Make dey do the same work. A trigger go fire, data go move between APIs, and something go land for another system. The choice between dem usually depend on one thing: the billing unit. Zapier and Make dey charge for every unit of work wey your automations perform. Self-hosted n8n no dey charge per unit of work, because na server you dey pay for instead.

Na this one difference dey drive everything wey follow. Metered plan fit cost almost nothing when you run ten workflows per day, but e go become your biggest software expense when workflow start to fire every minute. Flat server cost dey do the opposite: e fit look expensive on day one, but e no go change as volume dey increase. None of the two models dey dishonest. Na only say dem dey bill different people better.

Wetin each product dey charge for

Zapier dey bill per task. Zapier own definition be say dem count task anytime Zapier successfully finish one unit of work. Each successful action step for one Zap dey use one task, and some actions dey use more than one. Triggers and polling no dey count, failed actions no dey count, and the built-in tools (Formatter, Paths, Filter, Delay, Looping, Storage) no dey count. So, one Zap wey get one trigger and three action steps go cost three tasks every time e run. As of July 2026, the free tier get 100 tasks every month, and the paid Professional plan start around 20 US dollars every month when dem bill yearly, for 750 tasks.

Make dey bill per credit, na the unit wey e bin dey call operation before. Make documentation talk say each action wey one scenario perform dey use a certain number of credits, and most actions dey use one. Reading, searching, creating, updating, deleting, transforming, aggregating and iterating each cost one credit. Routers and error handlers no dey. The important word na iterating: one module wey dey loop through 200 rows go spend roughly 200 credits, no be one. As of July 2026, the free tier get 1,000 credits every month, and the Core plan start around 12 US dollars every month for 10,000 credits.

Self-hosted n8n no dey bill anything per execution. The Community edition free and e get almost the complete feature set. Workflow runs, nodes inside one run, loop iterations and retries all cost zero, because na only your server CPU, memory and disk dey get meter. Paid self-hosted tiers dey available and dem need a license key, but dem dey sell governance features like single sign-on and separate environments, no be throughput. If you don already set up n8n for one VPS with Docker and HTTPS, you don already pay the whole recurring bill.

The install command from n8n own docs short enough to show the point:

docker volume create n8n_data

docker run -it --rm \
 --name n8n \
 -p 5678:5678 \
 -e GENERIC_TIMEZONE="Europe/Berlin" \
 -e TZ="Europe/Berlin" \
 -e N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true \
 -e N8N_RUNNERS_ENABLED=true \
 -v n8n_data:/home/node/.n8n \
 docker.n8n.io/n8nio/n8n

The editor go then answer for port 5678. That command na only for first look, because e dey use the default SQLite file and --rm dey throw the container away when you stop am. Any server wey you depend on need Postgres and a reverse proxy for front.

Realistic month, wey dem count

Vague comparison no dey useful, because your volume na im dey determine the answer completely. So count am. Na four automations be these wey small company really dey run, together with how often each one dey run and how many billable steps each run dey perform.

[
  {
    "label": "Form to CRM to Slack",
    "runs_per_month": 1200,
    "billable_steps": 3,
    "units_per_month": "3,600"
  },
  {
    "label": "Order sync, every 15 min",
    "runs_per_month": 2880,
    "billable_steps": 4,
    "units_per_month": "11,520"
  },
  {
    "label": "AI inbox triage",
    "runs_per_month": 900,
    "billable_steps": 5,
    "units_per_month": "4,500"
  },
  {
    "label": "Daily revenue report",
    "runs_per_month": 30,
    "billable_steps": 6,
    "units_per_month": "180"
  }
]

The order sync alone dey use 11,520 billable units every month, because schedule trigger wey dey run every 15 minutes dey fire 2880 times, and each run dey touch 4 paid steps. The daily report, wey fit look like the heavy workflow because e get the highest number of steps, dey use 180. Frequency dey beat complexity every time. Na why estimating from the workflow shape instead of the schedule fit make person receive invoice wey e no expect.

Together, those four automations dey use 19,800 billable units every month. For Zapier, this one go put you for the 20,000-task tier of a paid plan. For Make, e be roughly twice the credits wey Core plan include, so you go need buy higher plan. For self-hosted n8n, na the same monthly server bill as running one workflow, and the server no go notice.

Now change one number. Move the order sync from every 15 minutes to every 5 minutes. Zapier and Make go triple that line to 34,560 units, and the invoice go move to the next tier. The n8n box go add just a few percent CPU. That difference, instead of the headline price of any plan, na the real decision.

Where the crossover dey

No universal break-even point dey, but the pattern dey predictable.

• Below roughly 1,000 units per month, hosted free tiers win completely. Nothing beat zero, and you no get server wey you need patch.
• Between roughly 1,000 and 10,000 units, entry paid plans cheap, and hosted tools still give better value, because VPS plus your attention cost more than 12 to 20 dollars per month.
• Above roughly 20,000 units per month, metered billing dey add up, and fixed server cost usually win. E go continue to win as volume dey grow.
• Any workflow wey dey iterate over rows (a CSV import, a list of 500 orders, a paginated API) dey skip those ranges completely, because one run fit spend thousands of units.

Na this last case make self-hosting stop to be just preference. A nightly job wey processes 5,000 records go use 5,000 credits for metered plan, but e go use CPU for only one execution on n8n.

The same logic apply to AI steps, wey automation volume dey grow fastest for. Every model call inside hosted scenario na billable unit on top of the model provider own token charge, so dem dey meter you twice for the same work. Running the Claude API inside n8n workflows mean say you go pay only the model provider.

n8n license wey dem explain clear

n8n no be open source under the usual definition, and to pretend say e be so na how people dey get surprise later. E dey release under Sustainable Use License, wey talk say:

You fit use or modify the software only for your own internal business purposes or for non-commercial or personal use.

And about passing am to other people:

You fit distribute the software or provide am to other people only if you do am free of charge for non-commercial purposes.

Compare this with wetin you plan to do. If you run n8n to automate your own company work, na internal business purposes be that. E dey allowed, and this one cover almost everybody wey dey read this. If you run n8n as the engine behind product wey you dey sell, or you resell hosted n8n instances to customers, the free license no cover am. You need commercial agreement with n8n. Check the current LICENSE.md for the n8n repository before you build business on top of am, because terms fit change and na only the text for the repository count.

Another smaller issue dey. The free Community edition get almost every feature, and free registration unlocks some extra ones, like folders and debug for editor. Features wey target bigger teams, including single sign-on, log streaming and separate environments, dey behind paid license key. Those ones na governance features. Throughput no be wetin dem dey sell.

Wetin the flat server cost no cover

The honest version of the self-hosting argument includes the parts wey no be free.

You own uptime. When hosted platform get outage, you wait and another person dey paged. When your VPS get outage, na you go fix am, no matter the hour wey e happen. You own upgrades, because n8n releases dey come often and container image wey you never update go become security problem. You own backups: n8n encryption key and Postgres database together na the only copy of your credentials and workflows, and if you lose the key, every stored credential go become unreadable. Point encrypted restic backups to both from the first day, no be from the first incident.

You still own the parts wey hosted plan quietly include. Zapier and Make maintain thousands of app connectors and repair dem when vendor change API. n8n get large node library and generic HTTP node wey cover the rest, but broken integration fit take your whole afternoon. Hosted plans still include compliance paperwork, support with response time, and another person’s on-call rotation.

Budget the real number honestly: the server, plus about one hour every month for maintenance, plus the day wey you go spend for the initial setup. If that total still lower than the metered invoice, self-hosting na the right choice. At 19,800 units every month, e usually dey. At 500 units every month, e usually no dey.

Which one you suppose choose

Choose Zapier when na the connector list be the main product. E get the widest app coverage and the easiest learning curve. If your automations dey short and dem no dey happen often, per-task billing fit really cheap.

Choose Make when your logic dey visual and e get branches. Its canvas dey handle routers, iterators and error handlers well. Its credits cost less per unit than Zapier's tasks for similar tiers. Monitor the iterators, because na there credit usage fit grow without warning.

Choose self-hosted n8n when volume high, when data no fit leave your own infrastructure, or when workflows dey call models and databases wey you already dey run. Na also the only one among the three wey you fit read the code path wey workflow dey take and change am. Budget for one VPS and 1 hour every month, and read the license first. E deserve place for any 2026 self-hosting shortlist because of this reason: the meter stops.

FAQ

Self-hosted n8n really free dey?

Community edition free to run, and e no dey charge per execution. E get almost all the features. You still go pay for the server. Features wey bigger teams dey use, like single sign-on, log streaming and separate environments, need paid license key. Dem no dey measure your workflow volume for billing, and na the main reason people dey self-host.

How many Zapier tasks one Zap dey use for each run?

E dey use one task for each successful action step, but some actions fit cost pass one. Trigger free, polling free, failed actions free, and built-in tools like Formatter, Paths, Filter and Delay free. So, if one Zap get trigger and three actions, e go cost three tasks per run. If e run 1,000 times for one month, na 3,000 tasks.

Make credits and Zapier tasks dey count the same way?

Dem close, but dem no be exactly the same. Both dey charge for each action wey workflow perform. Make dey count each module action as one credit, including transformations and every iterator pass. Zapier no dey charge for e own built-in formatting and filtering tools. The difference dey matter most for workflows wey loop through lists, because Make per-iteration counting dey increase fast.

I fit use self-hosted n8n inside commercial product?

No, not under the free license. Sustainable Use License allow use for your own internal business purposes, or for non-commercial or personal use. Automating your own company work dey okay. But if you embed n8n inside product wey you sell, or resell hosted instances, you need commercial agreement with n8n. Read the current LICENSE.md for the repository before you commit to a design.

For what volume I suppose switch from Zapier or Make to n8n?

No fixed number dey, but the pattern still dey hold. Below about 1,000 billable units per month, hosted free tiers dey win. Above about 20,000 per month, fixed server cost usually dey win. Any workflow wey dey iterate over rows fit break this rule immediately. One run over 5,000 records go spend 5,000 units for metered plan, but e no go spend anything extra for your own server.