Published 2026-10-16, updated 2026-10-16. Prices checked 2026-10-16.
How many Make credits do you need?
Multiply your monthly runs by the number of modules in each run (trigger included). Routers and error handlers don’t use credits. A 5-module scenario that runs 1,500 times a month uses 7,500 credits, which fits Make Core’s 10,000-credit level at $9/month on annual billing.
Open the calculator pre-filled for 1,500 runs × 5 modules →
Disclosure: some links are affiliate links. If you buy through them we may earn a commission, at no extra cost to you. Our ranking always shows the cheapest option first.
How Make counts credits
You use 1 credit for each module action, including the trigger or webhook read, iterators and aggregators. Routers and error handlers cost 0 credits (Make help, read 2026-10-16). If an iterator loops over items, every module after it runs once per item.
Credits per month = runs × (trigger + action modules + iterator/aggregator modules)
Prices (USD per month, annual / monthly billing)
| Credits/mo | Core | Pro | Teams |
|---|---|---|---|
| 10,000 | $9 / $10.59 | $16 / $18.82 | $29 / $34.12 |
| 20,000 | $16 / $18.82 | $29 / $34.12 | $53 / $62.35 |
| 40,000 | $29 / $34.12 | $53 / $62.35 | $99 / $116.47 |
Source: make.com/en/pricing. Monthly figures were read with the monthly toggle on make.com/en/pricing, 2026-10-16.
Two gotchas
- Higher plans don’t add credits. At the same credit level, Pro and Teams cost more for features, not volume.
- When you run out, scenarios stop until you buy more credits or upgrade.
Related
- Make pricing explained
- Make vs n8n · Zapier vs Make
- What happens when you run out of Zapier tasks?
- Self-hosted n8n: the true monthly cost
Prices checked 2026-10-16