Make.com Credits Explained: Stop Burning Credits in 2026

Affiliate disclosure: This post contains affiliate links. If you buy through them, we may earn a commission at no extra cost to you. We only recommend tools we’d run our own business on.

What one credit actually is

The rule is one sentence long: every time a module in your scenario performs an action, that’s one credit. Reading a Pipedrive record: 1 credit. Writing a Google Sheets row: 1 credit. Searching, updating, deleting, transforming data with built-in tools, aggregating, iterating — each costs a credit per execution (all confirmed on Make’s pricing page, checked October 2026).

Contents

What one credit actually is
The plans, priced (checked October 2026)
The iterator trap: where credits die
What’s free, what’s not: the cheat sheet
The 7-step credit audit checklist
FAQ
Methodology
Sources

A few things that cost zero credits, also straight from Make’s FAQ:

The trigger — the module that starts the scenario is free
Router modules — no credits counted
Error handlers (Rollback, Break, Resume, Commit, Ignore) — no credits counted
Paths a filter blocks before any module downstream runs
A scenario that errors out before any module executes

That’s the entire accounting model. The trap is that it feels like you’re paying per workflow run, the way n8n bills per execution. You’re not. You’re paying per module step, and loops multiply.

The plans, priced (checked October 2026)

Magnifying glass and string loop — hidden cost multiplier

Plan	Price (checked Oct 2026)	Credits/month	Key limits
Free	$0	1,000	2 active scenarios, 15-min minimum scheduling
Core	$9/mo annual ($10.59 monthly)	10,000	Unlimited scenarios, 1-min scheduling, Make API
Pro	$16/mo annual ($18.82 monthly)	10,000	Priority execution, custom variables, full-text log search
Teams	$29/mo annual ($34.12 monthly)	10,000	Team roles, shared templates
Enterprise	Custom	Scales to 8M+	SSO, overage protection

Two structural facts matter more than the sticker price:

Plan tier and credit volume are separate decisions. Every paid tier starts at 10,000 credits — you pay up for speed, file size, and collaboration, not for volume. Running out of credits doesn’t mean you need Pro; it means you need more credits or less waste.
Make charges about $0.0009 per credit at Core scale ($9 ÷ 10,000). Compare that to Zapier’s ~$0.027 per task and the gap is obvious. But the gap only matters if you count your steps honestly.

One honesty note: when we loaded make.com’s own pricing page on October 8, 2026, Core displayed as $12/mo. Third-party pricing trackers checked within the last 48 hours still show $9 annual / $10.59 monthly. The live page may have been showing a different billing cadence or a fresh price test — check the annual/monthly toggle on the live page before you buy, because the published numbers are clearly in motion.

⚠️ Price wobble in effect: Make cut paid-tier prices ~25% in September 2026 (Core $12 → $9) without a formal announcement. If you’re budgeting, re-check the live page and screenshot your quote.

If you’re starting fresh, the move is simple: [AFFILIATE LINK: make] on the Core annual plan — 10,000 credits a month is the cheapest serious starting point in this category, and you can audit your way down from there.

The iterator trap: where credits die

This is the most expensive line in the entire pricing model, and Make’s own docs state it plainly: iterating over a row of data costs credits, per item processed. Any module inside a loop runs — and bills — once per item.

Here’s a concrete example. You run a WooCommerce store and built this scenario:

Watch orders (trigger) — 0 credits
Iterator over the order’s line items — 1 credit per item
Search for the product in Google Sheets — 1 credit per item
Create an invoice line — 1 credit per item
Send data to your CRM — 1 credit per item

With a typical order of 6 line items, that scenario costs:

6 items × (1 iterator + 3 action modules) = ~18 credits per order

Not one credit per order. Eighteen. At 500 orders a day, that’s 9,000 credits per day — your entire 10,000-credit Core allowance, gone in about 27 hours. Over a 30-day month that’s roughly 270,000 credits, or about $243 at Core’s per-credit rate. A scenario most people estimate at “a few thousand credits” is really a quarter-million.

AWL verdict: Before you trust any credit estimate, count the loops. Modules × items per run × runs per month. Every audit we describe below starts with this formula, because the iterator line is where every blown budget we’ve ever seen begins.

Two more multipliers worth knowing:

Polling scenarios burn credits on every check, including the checks that find nothing. A scenario polling every minute for new rows costs 1,440+ credits a day just waking up.
Code execution isn’t 1 credit. Make’s Code App bills 2 credits per second of code execution time (from Make’s own pricing page, checked October 2026). A 30-second script run inside a loop is 60 credits — not the 1 credit most people assume.

What’s free, what’s not: the cheat sheet

Burns credits	Free
Every module action (read, search, create, update, delete, transform, aggregate, iterate)	The trigger module
Each router path that actually runs modules	The Router module itself
Filters that evaluate and pass	Filters that block a path before modules run
Polling checks, even when nothing is new	Error handler modules (Rollback, Break, Resume, Commit, Ignore)
Code execution: 2 credits per second	—

The 7-step credit audit checklist

Run this on any Make account once a quarter. It takes under an hour and usually finds 20–40% waste.

Export the usage ledger. In Make, open your organization’s credit usage and sort scenarios by consumption over the last 30 days. Write down the top 5 — they almost always account for 80%+ of the bill.
Count steps per run. For each of the top 5, count the billable modules in one execution. Don’t eyeball it — actually count.
Hunt the loops. Open every iterator, repeater, and aggregator. Multiply modules-inside-the-loop × average items per run. If the loop average is a guess, check 10 recent executions and average them.
Kill the dead polls. For every scheduled scenario, ask: does the source offer a webhook? If yes, switch to it. A minute-interval poller burns 43,200 credits a month before doing a single useful thing.
Move filters upstream. A filter that blocks a path after three modules ran just paid for three modules. The same filter before them costs nothing when it blocks. Filters should be the first thing after the trigger wherever possible.
Batch the loops. If an API accepts multiple records in one call (Sheets append rows, many CRMs accept batch writes), replace the iterator + single-write pattern with one batch call. Fifty items becomes one module execution instead of fifty-plus.
Delete the ghosts. Every account has scenarios still running for processes that ended months ago — the old launch, the ex-employee’s onboarding flow, the test poller. Deactivate anything with no owner.

If you’re migrating off a tool that’s shutting down and rebuilding in Make, watch the loops extra carefully: rebuilds are where iterator traps get imported by accident. (See our Relay.app migration guide for the full moving checklist.)

FAQ

Q1: Is a “credit” the same as the old “operation”?
Yes. Make renamed the unit on August 27, 2026, and the billing behavior is identical: one module action = one credit. Older tutorials that say “operations” still describe the current system correctly.

Q2: Why did my scenario stop running in the middle of the month?
You ran out of credits. Make notifies you at 75% and 90% of your purchased credits, then scenarios pause until credits are added. Incoming webhooks queue up and are processed once you top up — you don’t lose the data, but nothing executes in between.

Q3: What happens when I run out — can I buy more without upgrading?
Yes. You can buy extra credits in bundles of 1,000 or 10,000 at the price defined in your subscription, or turn on auto-purchasing of 10,000 credits before you run dry (Core, Pro, and Teams plans). Credits expire at the end of the billing term, so don’t stockpile far ahead of actual need.

Q4: Do triggers really cost nothing?
The trigger module itself costs nothing. But be careful: a trigger that runs a polling check (searching for new records on a schedule) still bills for the modules that execute during that check. Only webhook-style instant triggers are truly zero-cost.

Q5: I use Make’s AI features — is it still 1 credit per action?
Not always. Make’s own FAQ states that “some advanced features leveraging Make’s AI Provider may use more” than 1 credit, and the Code App explicitly bills 2 credits per second of execution time. If your scenarios lean on AI steps, audit those separately — they don’t follow the 1:1 rule.

Methodology

All prices and billing rules were verified on October 8, 2026. Plan prices came from third-party pricing trackers re-checked against Make’s pricing page within the last week. The credits-vs-operations rename date (August 27, 2026), the free exceptions (router, error handlers), the bundle sizes, and the 2-credits-per-second code billing came directly from make.com/en/pricing, which we loaded and read on October 8, 2026. The iterator math uses a 6-line-item average order and 500 orders/day as a representative mid-size store. The ~$243/month figure for 270,000 credits assumes Core’s per-credit rate of $0.0009 and ignores volume discounts.