Guide
Make credits explained, using one workflow we actually ran
A credit is what Make charges you for a module doing something. The useful question is not the definition — it is how many you will get through. We built one ordinary workflow and it cost 13 credits per run. Here is where every one of them went.
No link on this page is an affiliate link. We are in the programme below, so we could earn a commission elsewhere on this site — but not from anything on this page. We recommend free tools where they are the better answer, including ones that earn us nothing.
- Make.com: 35% of subscription payments for 12 months; extra-operation purchases do not earn commission (terms verified 2026-09-24)
What counts as a credit
DocumentedMake’s help centre states that, by default, one operation equals one credit. (Make help centre, accessed 2026-09-24)
The word “operation” is doing the work in that sentence. An operation is a module doing its job once. A module that processes ten items generally does its job ten times, which is why the bill tracks the shape of your data rather than the size of your diagram.
You will see it written that Make renamed operations to credits on a specific date. We are not repeating a date here: Make’s own credits page does not state one, and we are not going to source a factual claim about a vendor from a third-party blog.
Where our 13 credits went
The workflow: receive an order, fetch its line items, write one row per line item. We pointed it at an endpoint we built and control, so every request was confirmed in our own server logs. Free plan, zone us2, 2026-09-22.
| Step | Credits | Why |
|---|---|---|
| Trigger | 1 | Receiving the order. |
| Fetch line items | 1 | One call, whatever it returns. |
| Iterator | 1 | Splitting the order into its lines. |
| Write row (×10) | 10 | One per line item. This is the part that scales. |
| Total | 13 | For a ten-line order. |
We tested itIn our tested 10-line workflow a successful fan-out cost 13 credits: 1 trigger + 1 fetch + 1 iterator + 10 per-line writes. Cost scaled with line items, which your customers control.
That last clause is the practical point. Three fixed credits plus one per line means your bill is set by how big your customers’ orders are, not by how complicated your scenario looks.
How to estimate your own usage
For a workflow shaped like ours, the arithmetic is fixed steps + (items × per-item steps). Ours was 3 + (items × 1). If you write to two destinations per line, it becomes 3 + (items × 2).
Count the modules that run once per run, count the modules that run once per item, then multiply the second group by a realistic item count — not your average, your bad month. The failure numbers below are why.
What a failing run cost
We tested itIn our tested 10-line workflow a completely failing run cost 4 credits against 13 for the identical successful run — Make stopped at the first failing item rather than attempting the rest.
We tested itA run that failed on a duplicate cost the same as a successful run, and a configuration error that never left Make still cost 4 credits.
We tested itIn our test, three automatic in-run retries of a failing HTTP step were billed as a single operation.
So yes, broken runs cost credits — but in this test Make was the cheapest of the three platforms to fail on, because it stopped early. The full three-way comparison is in do failed automation runs cost money?
What people get wrong about this
- Counting modules instead of items. A four-module scenario is not four credits if one of those modules runs per line item.
- Assuming every module costs the same. It does not — see the limitation below.
- Comparing credits to another platform’s number. The same workflow cost 13 credits on Make, 1 execution on n8n Cloud and 11 tasks on Pabbly. Those units do not convert — here is why.
Limitations of these numbers
Limitations and failure cases
- One workflow, built from standard modules, run on a free plan in zone us2 on 2026-09-22. Not an average across accounts or plans.
- Make's own help centre states consumption is not uniform: AI and advanced modules can consume differently, so a workflow built from those will not follow our arithmetic.
- We have not reproduced these figures on a paid plan or in another zone.
- We do not restate Make's plan prices here. They change, and we have not re-checked them since 2026-09-22.
- Vendors change billing behaviour. Treat this as dated evidence, not a permanent property of the product.
Where to go next
- Our full assessment of Make — including what we could not get it to do, and what it earns us.
- Make vs n8n — if you are choosing between the two rather than budgeting for one.
- The Automation Decision Sheet — the questions worth answering before you build the thing you are estimating. No email required.