Contents
At a glance
- Unit
- One module run against one bundle of data
- Current name
- Credit - Make states credits replaced operations as the billing unit term
- Baseline conversion
- 1 operation = 1 credit for most features
- Exceptions
- Some AI Content Extractor modules are fixed at 2 or 10 credits; some features are dynamic on tokens, files or pages
- Trigger modules
- Run once regardless of how many bundles they return
- Free plan
- 1,000 credits per month (checked August 2026)
- Rollover
- None - credits expire at the end of the term
Operations, and the rename to credits
Make historically billed in operations. Make's help documentation now states that credits replaced operations as the term for Make's billing unit, and that for most features one operation equals one credit. So the vocabulary changed and the arithmetic mostly did not. Make's pricing page describes a credit as what each action your scenario performs consumes, with most actions consuming one credit and some advanced features - particularly those using Make's AI provider - consuming more.
Two categories break the one-to-one baseline. Some Make AI Content Extractor modules have fixed credit usage above the default, with examples consuming two or ten credits per operation. And some features have dynamic credit usage tied to tokens, files or pages processed, so their cost varies with the payload rather than being a flat rate. If your scenario touches AI modules, the operation count and the credit count are no longer the same number.
The counting rule that decides your bill
The important mechanic in Make is bundles. A trigger module runs once regardless of how many bundles it returns. Every module after the trigger runs once per bundle. That is multiplication, and it is where Make bills diverge from expectations.
A five-module scenario that processes ten records is not five operations, it is roughly forty-one: the trigger once, then four modules times ten bundles. Scale that to a trigger returning 500 rows and a modest scenario becomes 2,000 operations in a single run.
This is why the highest-leverage optimisation in Make is filtering immediately after the trigger. A filter that discards nine of every ten bundles cuts everything downstream by 90%. Aggregators do the same job in reverse, collapsing many bundles back into one before an expensive module.
Plans and expiry
Make's pricing page in August 2026 lists a Free plan at 1,000 credits a month, and Core, Pro and Teams each starting from 10,000 credits a month at $9, $16 and $29 a month respectively, with Enterprise on custom pricing. Higher credit volumes are available within each tier. Credits expire at the end of the term and do not roll over. Extra credits bought as bundles expire after one month on monthly plans, or after one year on annual Pro and Teams plans.
The tiers are stacked so that the same credit volume costs more on a higher plan - you are buying features, not more credits, when you move from Core to Pro. Work out which features you actually need before you assume the higher tier is the one for volume.
What you should know
Compare Make against Zapier tasks and n8n executions only after modelling one real scenario end to end, because the units do not translate - see execution vs task vs operation. A workflow that is cheap on Make (low volume, few modules) can be expensive on n8n if it fires constantly, and a bundle-heavy scenario that is ruinous on Make is free of extra charge on n8n.
Also check the AI modules specifically before you commit. Dynamic credit usage tied to token counts means an AI step's cost is a function of your data, and a scenario tested on a short document behaves very differently on a long one.
Make operation FAQ
What is one operation in Make?
One module run against one bundle of data. The trigger module runs once no matter how many bundles it returns, but every module after it runs once per bundle, so bundle count multiplies the cost of everything downstream.
Did Make change operations to credits?
Yes. Make's help documentation states that credits replaced operations as the term for its billing unit, and that for most features one operation equals one credit. The counting mechanic is unchanged; some AI modules now consume more than one credit per operation.
Why did my Make scenario use so many credits?
Bundles. A trigger returning 200 records through a scenario with four modules after it is roughly 801 operations, not five. Add a filter immediately after the trigger so discarded bundles never reach the expensive modules, or use an aggregator to collapse bundles before them.
Do Make credits roll over?
No. Make states that credits expire at the end of the term. Extra credits bought as bundles expire after one month on monthly plans, or after one year on annual Pro and Teams plans.
How much do Make plans cost?
As listed in August 2026: Free at 1,000 credits a month, Core from $9 a month, Pro from $16 a month and Teams from $29 a month, each starting at 10,000 credits, with Enterprise custom. Higher credit volumes are priced within each tier, so moving up a tier buys features rather than volume.
Do Make AI modules cost more than one credit?
Some do. Make documents that certain AI Content Extractor modules have fixed usage above the default, with examples at 2 and 10 credits per operation, and that some features consume credits dynamically based on tokens, files or pages processed. Check the specific module before you scale a scenario that uses one.
Primary source
Make - credits and how they are counted
Checked August 2026. Anything priced or rate-limited moves, so verify against the source before you budget.
Want this built rather than explained?
Knowing what make operation means is one thing; having it running in your business is another. We scope one workflow at a time, quote a fixed price in writing after a free consult, build it, and hand it over with documentation you own.
