Make.com Review: Per-Operation Pricing, the Visual Builder, and Who It Beats
A cost-first look at Make for ops-savvy teams running 5k-500k automation runs a month — what an operation actually costs, what the 2025 credits switch changed, and where Zapier or self-hosted n8n win instead.
What Make actually is
Make (formerly Integromat) is a managed, visual automation platform: a drag-and-drop canvas where you wire apps together into scenarios using routers, iterators, aggregators and error handlers across thousands of integrations. It competes directly with Zapier on the managed-SaaS axis and with self-hosted n8n on the cost axis.
The headline difference from Zapier is the billing unit. Zapier charges per completed task and makes filters and its Formatter free. Make charges per operation — and an operation is one module run, every time the scenario fires (Trackstack, 2026-05-30). That single design choice drives everything about Make's economics.
How per-operation pricing works (and where it bites)
Every module that executes counts: the trigger, each filter, each router branch, and — the one that surprises people — each item passing through an Iterator or Aggregator can consume its own operation (Trackstack, 2026-05-30). So a Make scenario will report a far higher operation count than the equivalent Zapier task count for the same work.
The payoff is that each unit is cheap — roughly $0.001/op on the $9 Core plan ($10.59/mo equivalent for 10,000 ops; Trackstack, 2026-05-30). For a multi-step flow, per-op × many-modules still lands below Zapier's per-task × per-zap-run. The trap is volume amplification: polling triggers and loop-heavy scenarios can quietly multiply your operation count. Webhooks, which only fire on real events, are strongly preferred. (Note: specific claims that polling burns thousands of ops/month appear in secondary review content and aren't verified against a primary Make doc.)
The 2025 'operations to credits' switch
On 27 Aug 2025, Make changed its billing unit from operations to credits. Balances converted 1:1 automatically and plans/prices were unchanged (Make Community, 2025-08-13). Standard automations still cost 1 op = 1 credit.
"We're transitioning from operations to credits as our new billing unit. This change goes live on August 27th. The conversion is automatic, and there is no action required from you. Your current plan and price stay exactly the same."
— Misha (Make staff), Make Community forum, 2025-08-13
The substance of the change: AI/native-AI and some advanced features can now bill at a rate that exceeds 1 credit per run. That variability is the main post-2025 cost complaint from solo and indie operators:
"the idea of unpredictable, metered costs feels like a door closing... it may eventually price out the very creators, artists, and solo entrepreneurs who use Make."
— RuffKutts, Make Community forum, 2025-08-21
Disclosure: we substituted these two immutable Make Community permalinks because no usable 6-field Reddit permalink surfaced on this topic.
Plans and the real cost at scale
Make's paid tiers all start at a 10,000-op base: Free ($0 / 1,000 ops), Core ($9/mo), Pro ($16/mo), Teams ($29/mo), Enterprise custom (make.com/pricing, 2026-05-30). Included ops are identical across Core/Pro/Teams at the base tier — the higher tiers buy features (priority execution, team roles, audit logs, live chat support), not more ops. Annual billing saves 15% or more (make.com/pricing, 2026-05-30).
One pricing watch-out: extra-operation packs run ~25% more than included credits (a 10k-op pack ~$11 per the Nov 2025 update), and overage can auto-purchase — a surprise on a $9 Core plan (Trackstack, 2026-05-30).
The wedge is the cost curve, not exact high-volume stickers. Make exposes higher-volume figures only through an interactive slider that surfaces no published numeric prices, so we do not quote a flat 50k or 500k price — those are not publicly listed. What is verifiable: the Core unit cost (~$0.001/op) means the metered bill scales roughly linearly with usage, while a self-hosted n8n VPS is flat. The n8n row below is a general infrastructure reference range (typical small-VPS pricing), not a vendor-published or like-for-like figure (ops ≠ self-host executions).
| Volume/mo | Make (Core) | n8n self-host (reference) |
|---|---|---|
| 5,000 | $9 (annual; ~$10.59/mo equiv.) | ~$4-6 VPS (estimate) |
| 50,000 | not publicly listed (slider-only; meter scales ~linearly at ~$0.001/op) | ~$6-12 VPS (estimate) |
| 500,000 | not publicly listed (slider-only) | ~$12-20 VPS + a few maint. hrs (estimate) |
Read it this way: at 5k Make is effectively free-tier-adjacent and not worth self-hosting for. As volume climbs, Make's metered bill grows with usage while a flat VPS does not — so at high volume self-hosting wins on cost, if you have the maintenance capacity. We deliberately don't put a hard dollar figure on Make's 50k/500k tiers because Make doesn't publish one.
The visual builder: more power, steeper curve
Make's canvas is its strongest selling point against Zapier. Routers let one trigger fan out into conditional branches; iterators and aggregators split and recombine data; error handlers add resilience. For complex, multi-branch, data-transform flows, review consensus rates Make as more capable than Zapier (G2, 2026-05-30).
The cost is onboarding. The top complaint versus Zapier — whose builder gets people running quickly — is the learning curve around iterators and aggregators. Live chat support is also gated to higher tiers, so Core/Pro users lean on docs and the community. If your flows are genuinely linear and simple, Make's power is overhead you'll pay for in ramp time.
Who Make fits — and who should pick Zapier or n8n
Pick Make if you're an ops-savvy SMB running multi-step or multi-branch workflows, you want lower cost-per-action than Zapier, and you'll invest in the builder. Per-op << per-task makes Make cheaper than Zapier for anything beyond a two-step zap — just design around webhooks, not polling.
Pick Zapier if speed-to-launch and breadth of no-fuss integrations matter more than unit cost, your flows are simple/linear, and you'd rather not learn iterators. Zapier's free filters/Formatter also blunt Make's per-op advantage on lighter automations.
Pick self-hosted n8n at high volume if you can run a small VPS with a few maintenance hours: it's flat-cost and unmetered, so the economics flip in its favor as run counts grow. Note that n8n self-host is unmonetized — if you'd rather stay managed, n8n Cloud (trial) is the hosted route. Otherwise, if Make is your pick, you can start on Make's free 1,000-op tier and upgrade to Core only when you outgrow it.
Disclosure: links to Make and n8n Cloud are affiliate links — we may earn a commission at no cost to you. Zapier, Automatisch, Kestra and Windmill are editorial mentions with no affiliate relationship.
What real users say
We're transitioning from operations to credits as our new billing unit. This change goes live on August 27th. The conversion is automatic, and there is no action required from you. Your current plan and price stay exactly the same.
the idea of unpredictable, metered costs feels like a door closing... it may eventually price out the very creators, artists, and solo entrepreneurs who use Make.
FAQ
What is an 'operation' in Make, and how is it different from a Zapier task?
An operation is one module run — every time the scenario fires, the trigger, each filter, each router branch and each item through an iterator/aggregator can each count as an operation (Trackstack, 2026-05-30). Zapier instead charges per completed task and makes filters and Formatter free. Make's op counts therefore run higher, but each op costs far less (~$0.001/op on Core), so multi-step flows are usually cheaper on Make.
Did Make get more expensive after the 2025 credits switch?
For standard automations, no — the 27 Aug 2025 switch converted balances 1:1 and left plans and prices unchanged, with 1 op still equal to 1 credit (Make Community, 2025-08-13). What changed is that AI/native-AI and some advanced features can now cost more than 1 credit per run, which is the main source of post-2025 unpredictability complaints from solo users.
How much does Make cost at 50k or 500k operations a month?
Make publishes flat prices only for its 10,000-op base tiers (Core $9/mo, Pro $16/mo, Teams $29/mo annual; make.com/pricing, 2026-05-30). Higher volumes are configured through an interactive slider that does not surface published numeric prices, so a flat 50k or 500k figure is not publicly listed. Given the Core unit cost (~$0.001/op), the metered bill scales roughly with usage; extra-op packs carry a ~25% markup (~$11 per 10k, Nov 2025).