The short answer
- check_circlen8n bills per workflow execution, Zapier bills per completed action (task), and Make bills per module operation (credit), so a 10-step AI agent run costs 1 unit on n8n and roughly 10 on Zapier or Make.
- check_circleAt 2026 annual list prices, n8n Cloud Starter is about €20/month for 2,500 executions, Zapier Professional starts around $19.99/month for 750 tasks, and Make Core starts around $9/month for 10,000 credits.
- check_circleFor AI agent workloads above a few thousand runs a month, n8n is usually the cheapest managed option; Zapier becomes the most expensive fastest because every agent step is a billable task.
- check_circleMove from no-code to custom code when you need automated tests and evaluations, state shared across runs, low latency, or agent logic that ships inside your own product — not merely to save on platform fees.
- check_circleThe pattern that works best for most teams is hybrid: a workflow tool handles triggers and integrations, and a small custom service handles the agent reasoning that needs testing and version control.
The straight answer by volume
Under about 500 agent runs a month, use whichever tool your team already knows — the bill will be small on all three. From roughly 500 to 5,000 runs, n8n is usually the cheapest managed option because it does not charge per step. Above tens of thousands of runs, or when reliability requirements rise, self-hosted n8n or a custom service usually wins.
| Runs per month | Default pick | Why | Watch out for |
|---|---|---|---|
| Under 500 | Tool you already use | Platform fees are small everywhere | Building habits that will not scale |
| 500-5,000 | n8n Cloud or Make | Per-execution or cheap per-credit billing | Zapier task counts climbing fast |
| 5,000-50,000 | n8n (Cloud Pro or self-hosted) or hybrid | Step-based billing gets expensive | Concurrency limits and debugging at volume |
| 50,000+ | Self-hosted n8n or custom service | Platform fees and limits dominate | You now own operations and on-call |
How each tool bills in 2026
The billing unit decides your cost more than the sticker price does. Zapier counts tasks: each successfully completed action step. Make counts credits: roughly one per module operation, with iterators and routers multiplying usage. n8n counts executions: one per workflow run, however many steps it contains.
- Zapier: most action steps count as a task; triggers do not. Overage is billed at a premium to your plan rate up to a cap, after which Zaps pause until the next cycle.
- Make: every module that runs uses credits. A loop over 20 items runs the modules inside it 20 times.
- n8n Cloud: a run is one execution regardless of steps. Plans also cap concurrent executions, which matters for bursty agent workloads.
- Self-hosted n8n: no execution meter; you pay for servers and the time to run them.
- Custom code: you pay for compute, usually a small container or serverless functions, plus engineering time.
Price side by side
Entry prices look similar; what differs is how far each plan stretches for an AI workload. The table shows 2026 entry plans and what they include.
| Option | Entry plan | Included | Billing unit | Notes |
|---|---|---|---|---|
| n8n Cloud | Starter ~€20/mo | 2,500 executions, 5 concurrent | Execution | Pro ~€50/mo for 10,000 executions and 20 concurrent |
| Zapier | Professional ~$19.99/mo | 750 tasks | Task (action step) | Team from ~$69/mo; higher task tiers cost more |
| Make | Core ~$9/mo | 10,000 credits | Credit (module operation) | Pro ~$16/mo, Teams ~$29/mo |
| n8n self-hosted | Community edition, free license | No execution cap | Your infrastructure | Server roughly $20-$150/mo plus ops time; paid tiers add SSO and environments |
| Custom service | No platform fee | Whatever you build | Compute | Build cost plus hosting, typically $20-$80/mo for a small service |
The AI agent multiplier
An AI agent run is rarely one step. A typical support agent receives a trigger, fetches the customer, calls the model, searches a knowledge base, looks up an order, calls the model again, updates the ticket and posts a notification — 8 to 15 billable steps for one logical run.
| Runs per month | Zapier tasks | Make credits | n8n executions |
|---|---|---|---|
| 500 | ~5,000 | ~5,000 | 500 |
| 5,000 | ~50,000 | ~50,000 | 5,000 |
| 50,000 | ~500,000 | ~500,000 | 50,000 |
Break-even: when custom code beats per-step billing
A small custom agent service costs roughly $10,000-$30,000 to build, plus hosting and 15-30% of build cost per year to maintain — on the order of $150-$800 a month all-in. It beats platform fees alone once your platform bill consistently exceeds that range.
With Zapier, that can happen at a few thousand agent runs a month because every step is a task. With n8n Cloud or self-hosted n8n, platform fees rarely get high enough to justify custom code on cost alone. That is why the honest reasons to go custom are usually capability, not price.
Self-hosting n8n honestly
Self-hosted n8n removes the execution meter but makes you the operator. The license is free; the work is not. Budget for it before assuming self-hosting is the cheap option — or have a cloud infrastructure team run it for you.
- Infrastructure: a VPS or container, a Postgres database, and Redis plus worker processes once you run queue mode at volume — roughly $20-$150 a month.
- Upgrades: n8n ships frequently. Someone must test upgrades against your workflows.
- Backups and recovery: the database holds workflows, credentials and execution history. Test restores, not just backups.
- Security: patching, network exposure, and safe storage of the credentials encryption key.
- On-call: when a workflow that sends customer emails stops at 2am, who notices and who fixes it?
- Licensing: n8n uses a fair-code license. Internal use is fine; offering n8n itself as a hosted service to others is restricted.
Where no-code breaks
Workflow tools strain under AI agents in six specific places. If two or more apply to you, plan for at least part of the logic to live in code.
| Requirement | What goes wrong in a workflow tool | What code gives you |
|---|---|---|
| Long-running jobs | Step and execution timeouts, awkward waits | Background jobs with checkpoints |
| Retries and idempotency | Partial runs repeat side effects such as duplicate emails | Idempotency keys and controlled retries |
| Shared state across runs | Workarounds via external tables and lookups | A proper database model |
| Concurrency | Plan limits and race conditions on shared records | Queues and locks you control |
| Versioning and review | Visual diffs are hard to review; changes go straight to production | Pull requests, code review, rollbacks |
| Testing and evaluation | Little support for automated test suites | Unit tests and model evaluation sets in CI |
Where no-code wins outright
Do not pay to custom-build workflows that are simple, low-volume and made of standard integrations. These five almost always belong in a workflow tool:
- 1Form submissions into a CRM with a notification.
- 2New deal or ticket alerts into Slack or Teams.
- 3Invoice and payment syncing between billing and accounting tools.
- 4Lead enrichment with a single lookup and a model-written summary.
- 5Scheduled report emails assembled from one or two sources.
Reliability and observability
For agent workflows you need to answer three questions quickly: what did it do, why, and did quality change after the last edit. Workflow tools answer the first reasonably well through execution logs; the second and third usually need additions.
Whatever you choose, log the model inputs and outputs for each run with sensible retention, keep a labeled evaluation set of real cases, and re-run it whenever prompts or models change. That discipline matters more than the platform.
EU and UK buyers: residency and sub-processors
If you process EU customer data, check where each tool stores and processes it and list it as a sub-processor. Make offers EU hosting options, n8n is a Berlin-based company whose self-hosted edition runs wherever you deploy it, and Zapier is US-based, so transfers need the usual safeguards.
Self-hosting in an EU region often settles procurement questions fastest because data residency is then something you control directly. Confirm each vendor's current data processing terms before relying on this summary.
Lock-in and exit cost
No workflow format moves cleanly between Zapier, Make and n8n; migrations are rebuilds. What does carry over is everything outside the tool: prompts, evaluation sets, API credentials, documentation of each workflow's purpose, and any logic you already moved into code.
Keep prompts and business rules in a version-controlled place rather than pasted into steps, and a future migration becomes days of rewiring instead of weeks of rediscovery.
The hybrid pattern we ship most
Most production agent systems we build are hybrid: n8n or another workflow tool handles triggers, schedules and integrations, and a small custom service handles the agent reasoning — prompts, tool calls, validation and evaluation — behind a single API endpoint.
This keeps the parts that change often and need testing in code with version control, while operations staff can still adjust triggers and integrations visually. Our AI automation service is usually scoped this way.
Decision tree: seven questions
Answer these in order; the first "yes" that points to code usually settles the architecture.
- 1Does the agent logic ship inside your own product for customers? Yes: custom code.
- 2Do mistakes have financial, legal or customer-facing consequences? Yes: code for the reasoning, with evaluations and approvals.
- 3Do you need state shared across runs? Yes: code or a hybrid with a real database.
- 4Will volume exceed about 5,000 runs a month? Yes: avoid per-step billing; use n8n or code.
- 5Is EU data residency a contractual requirement? Yes: self-host or choose an EU-hosted option.
- 6Does anyone on the team write and maintain code? No: stay on a managed workflow tool, or buy maintenance.
- 7Is the workflow still changing weekly? Yes: prototype in a workflow tool first, then harden.
Migrating off 40 tangled Zaps
Migrate by volume and risk, not all at once. Most teams find a handful of Zaps generate most of the task bill and most of the failures.
Inventory
Export the list of Zaps with monthly task counts, owner and what breaks if it stops.
Classify
Mark each as keep, rebuild in n8n, move to code, or delete. Expect a meaningful share to be deleted.
Rebuild the heaviest first
Start with the highest-task, highest-risk workflows where savings and reliability gains are largest.
Run in parallel
Run the new version in shadow mode, comparing outputs before switching off the old one.
Cut over one at a time
Switch per workflow with a rollback plan, and leave the long tail of trivial Zaps where they are.
A hybrid n8n-plus-custom agent project typically starts from our Build tier at $6,900 for one production automation; larger multi-workflow migrations are quoted to scope on the pricing page.
Frequently asked questions
Is n8n actually cheaper than Zapier for AI workflows?add
Usually, yes. n8n bills per workflow execution, while Zapier bills per completed action. An AI agent run with ten steps is one execution on n8n and roughly ten tasks on Zapier, so the gap widens quickly as volume grows. Self-hosted n8n removes the execution meter but adds operating work.
Can n8n replace a custom-built AI agent?add
For many internal workflows, yes — n8n handles triggers, model calls, tool calls, branching and retries well. It is a weaker fit when you need automated test suites, shared state across runs, low latency, or agent logic that ships inside your own product.
When should we move off Zapier?add
Common triggers are a task bill that keeps climbing because agent workflows have many steps, a single process spread across many chained Zaps, or failures that customers notice before your team does. Move the highest-volume and highest-risk workflows first and leave simple ones in place.
Is self-hosting n8n safe for client data?add
It can be, if you run it like production infrastructure: private networking, patching, encrypted backups, careful handling of the credentials encryption key, access control and monitoring. The risk comes from treating it as a side project rather than from n8n itself.
What does a hybrid n8n-plus-custom build cost?add
A hybrid with one production agent service and a handful of workflows commonly falls around $10,000-$25,000, and Solyio's Build tier starts at $6,900. Add hosting of roughly $20-$150 a month and model API costs, which depend on volume and model choice.
Does Make or Zapier charge for AI model usage?add
If you connect your own model provider API key, the provider bills you for tokens and the platform bills for its own units. Some platforms also offer built-in AI features that consume their credits or tasks, so check which option a workflow uses.
The engineers and architects who build Solyio's client platforms — web, mobile, cloud, and AI automation. Everything here comes out of shipped client work.