Guide · Make meter lexicon
Make credits and operations — what each word counts
Make-only lexicon. Live scorecard: Totals are not published yet. Self-hosted is a separate lane. No new scores.
Use this page if Make uses both words
Use
Use this page if…
You need what credits and operations count, and when 1 operation is not 1 credit. Quotes below were read 2026-10-01.
Skip
Skip if…
Dictionary: Tasks vs credits vs executions. Volumes: Same job, three meters. Ceiling: When you hit the meter. AI: How AI steps change the meter. Product: When Make is the right pick. A cheapest-tool list is not this page.
A use-or-skip check for Make’s two meter words.
- You see both credits and operations on Make and need which word is the bill.
- You will stay on Make’s words — what each one counts, and when they split.
Partner signup. We may earn a commission. Rankings are not sold.Try MakeTasks vs credits vs executions
Read more
What this page tells you. What the word credit counts on Make, what the word operation counts, and when those counts split. Companion to the three-tool dictionary, the 5-step job, the ceiling, and the AI delta. This page shows units and definitions only, with dated quotes from Make’s pricing page and Help Center, accessed 2026-10-01. It does not invent a monthly dollar. It publishes no annual savings. Verify before buy. It does not add new scores.
GuideSome scores not shown yetMake pages accessed 2026-10-01Affiliate · pc=stackscorecardLive scorecard
This page vs the other meter reads
Tasks vs credits vs executions is the three-tool dictionary. This page does not reprint Zapier tasks or n8n executions.
Same job, three meters counts one 5-step job at 50 / 500 / 5,000 runs. This page does not reprint that volume ladder.
How to meter automation is the watch list: usage, volume, and what multiplies a job. This page does not reprint that watch list.
When you hit the meter is the ceiling across Zapier, Make, and n8n. This page quotes Make’s own “credits run out” line, then stops.
How AI steps change the meter holds the token tables. This page names that some Make modules are not 1 credit per operation, then stops.
When free isn’t enough is the free or trial shape versus the first paid plan. This page names Free’s published credit quota and does not reprint the plan matrix.
This page is the Make lexicon. Two words. What each one counts. What it does not. When 1 operation is not 1 credit. Units only. It does not invent a monthly dollar.
The two words
Credits are what you pay. Operations are the module runs. Dated quotes below are from Make’s Help Center and are the spine of this page, accessed 2026-10-01.
Hub
Both words
In Make, credits and operations are related but distinct concepts. Operations count the activities performed in your scenarios, while credits are what you pay for those activities.
This is the Help Center hub that links the two articles. It does not add a third unit.
Credit
Credit
Credits are the currency you buy and consume to use Make. Only features triggered by scenario runs (apps, modules, and some in-app features) or the AI agent’s chat use credits.
The same page says credits replaced operations as the term for the billing unit, and that the two words stay separate: credits track what you spend, operations show the activity. By default, 1 operation equals 1 credit. That rate does not change with input size or data-transfer size.
Operation
Operation
An operation is a single module run to process data or check for new data.
A trigger runs once per check, however many bundles come back. An action runs once per bundle. The white bubble’s checkmark is the operation count. The coin is the credits those operations used. By default the bubble shows operations only. You can turn credits on next to the scenario name.
Hub: Make — credits and operations. Credit definition: Make — credits. Operation definition: Make — operations.
What each word counts, and what it does not
Read one word at a time. A blank on a page read 2026-10-01 stays —.
Swipe sideways on a narrow screen. Not a scored table.
| Word | What it is | Counts | Does not count | When the word is not 1 |
|---|---|---|---|---|
| Credit | The currency you buy and consume. Make’s pricing page says that as of August 27, credits are the billing unit. | By default, one operation. Only scenario-run features, or the AI agent’s chat, use credits. The pricing page’s short line: each module action, such as adding a Google Sheet row or fetching Gmail account data, counts as one credit. That FAQ also lists read, search, create, update, delete, transform with built-in tools, aggregate, and iterate as actions that count as credits. | Pricing FAQ: error-handler modules Rollback, Break, Resume, Commit, and Ignore — no credits counted. Router — no credits counted. A filter is not named on the credits, operations, credits-and-operations, or pricing pages read 2026-10-01: —. | Default is 1 operation equals 1 credit, and that rate does not change with file size. The credits page shows an example of fixed-rate modules tagged 2 or 10 credits per operation. Dynamic use varies by tokens, file size, page count, or run time. Make Code on Core, Pro, Teams, and Enterprise is 2 credits per 1 second of code execution time. Free’s cell on that pricing row was blank on this read: —. Token tables stay on Make’s credits page and on How AI steps change the meter. |
| Operation | One module run that processes data or checks for new data. The activity count, not the bill. | A trigger is one operation per check, however many bundles it returns. An action is one operation per bundle: five emails are five operations; three file uploads are three operations. Bundles from an earlier module multiply later modules. Make’s form example: the trigger returns 10 bundles, later modules run 10 times each, total 31 operations (1+30). | The operations page does not say a router, a filter, or an error handler sits outside the operation count: —. The pricing FAQ states the router and error-handler exceptions in credits. If you click Stop, the current module finishes its bundles and later modules do not run. | One check can return many bundles and still be 1 operation. The next module is one operation per bundle, not one for the run. Make’s sheets-and-email example is 11 operations, then 3 after a Text aggregator. That page prints operations. It does not print a credit total for the same run. |
Credit column: Make — credits and Make pricing, accessed 2026-10-01. Operation column: Make — operations. Pricing FAQ, as published: error-handler modules and the router — no credits counted.
When 1 operation is not 1 credit
The default on the credits page is 1 operation equals 1 credit. These rows are the published splits. They are not a 5-step inventory.
Swipe sideways on a narrow screen. Not a scored table.
| Object | Operation | Credit |
|---|---|---|
| Trigger check that returns many bundles | 1 operation per check. Make’s example: Google Sheet > Watch New Rows is 1 operation however many rows come back. | By default, 1 credit. The pricing short line also calls fetching account data one credit. |
| Send 5 emails, or upload 3 files | 5 operations, or 3 operations. One module run per bundle. | By default, the same count: 1 credit per operation. Google Drive > Upload a File is 1 credit per file on the credits page, file size aside. |
| Make Code on a paid plan | The operations page does not print a separate code-runtime rate: —. | Pricing table: 2 credits per 1 second of code execution time on Core, Pro, Teams, and Enterprise. Free’s cell on that row: —. |
| A module tagged above the default | Still one module run per bundle, unless the module’s own tag says otherwise. The operations page does not reprint those tags. | Not always 1. Credits page example: some fixed modules use 2 or 10 credits per operation. Dynamic modules vary by tokens, file size, pages, or run time. |
| Router, or an error handler | Not stated on the operations page read 2026-10-01: —. | Pricing FAQ: router — no credits counted. Error handlers Rollback, Break, Resume, Commit, Ignore — no credits counted. |
| A filter | Not named on the operations page read 2026-10-01: —. | Not named on the credits, operations, hub, or pricing pages read 2026-10-01: —. |
Non-AI apps, and third-party AI apps you connect yourself (the credits page names OpenAI, Anthropic Claude, and Gemini), stay on the default: 1 operation equals 1 credit. With a custom AI connection you pay that provider for tokens. Make’s AI Provider, on all plans in Make AI Agents and Make AI Toolkit, bills tokens and operations. An automatic AI connection (Make AI Web Search, Make AI Content Extractor, and the Simple Text Prompt modules named on the credits page) can include tokens, operations, and other usage. Token-per-credit rates are on Make — credits and on How AI steps change the meter. This page does not reprint that table. Verify before buy.
What the pricing page still says
As of August 27, credits are the billing unit in Make. Each action your scenario performs consumes a certain number of credits - most actions consume 1 credit, while some advanced features leveraging Make’s AI Provider may use more.
The same page asks “How many credits per month?” and answers that each module action, such as adding a Google Sheet row or fetching Gmail account data, counts as one credit. Free includes 1,000 credits per month. There is no time limit on the Free plan in that copy. The rest of the free-versus-paid read is on When free isn’t enough.
The usage-allowance section is written in both words. The intro says the allowance is proportional to credits purchased, and “for every 10,000 credits” you receive a set amount. The table header still says “per 10k operations licensed per month.” The worked example licenses 150,000 credits per month and lists 75 GB of data transfer, which is 15 times the published 5 GB per 10,000 credits. This page does not treat that header as a new unit.
The live scorecard still labels Make’s pricing model as operations per month, dated 2026-09-07. This lexicon does not edit that cell. A fixed monthly dollar from the pricing text read 2026-10-01: —. The page describes credits and plan features. This page does not transcribe a slider price.
When the credits run out
Make’s pricing FAQ: your scenarios will not continue to run until credits are added again. Make notifies you at 75% and again at 90% of purchased credits. Before the next cycle you can upgrade, buy extra credits in bundles of 1,000 or 10,000 at the fixed price defined in your subscription, or turn on auto-purchasing of 10,000 credits (Core, Pro, and Teams). The dollar of that fixed price, in the FAQ text read 2026-10-01: —.
Credits expire at the end of the term. Extra credits expire after one month on a monthly subscription, or at the end of one year on an annual Pro or Teams plan.
Hold, queue, and fail across Zapier, Make, and n8n stay on When you hit the meter. This page does not reprint that ceiling and does not invent an extra-credit dollar.
Don’t turn a word into a bill
A credit and an operation are units. A /500 score is not a plan. This page does not invent a converted list. It publishes no annual savings.
- Stay on the word until you can say what it counts and what it does not.
- Then open the three-tool dictionary on Tasks vs credits vs executions if the job also has to be said in Zapier tasks or n8n executions.
- Leave the volume ladder, the AI table, and the free plan on their own pages. This lexicon does not invent the dollar between the words.
Units and definitions only. Check the Make page on the day you buy.
How this sits on the scorecard
How this sits on the scorecard
Totals are not published yet.
If the question is whether Make is the product, see When Make is the right pick. If you already run the other tool, see Switching from Zapier to Make or Switching from n8n Cloud to Make.
Product link
Affiliate
Make
Sources
Primary Make pages only. Access date for every definition on this page: 2026-10-01. A fixed monthly dollar from the pricing text on that access date is —. We do not invent search volumes, testimonials, or a converted list.
- Make — credits and operations · accessed 2026-10-01
- Make — credits · accessed 2026-10-01
- Make — operations · accessed 2026-10-01
- Make pricing · accessed 2026-10-01
FAQ
What does a Make credit count?
Credits are the currency you buy and consume to use Make. Only features triggered by scenario runs, or the AI agent’s chat, use credits. Credits replaced operations as the name of the billing unit. By default, 1 operation equals 1 credit, and that rate does not change with file size. The pricing page’s short line says each module action counts as one credit. Error-handler modules (Rollback, Break, Resume, Commit, Ignore) and the router do not count credits. A filter’s credit cost on the pages read 2026-10-01: —. Accessed 2026-10-01.
What does a Make operation count?
An operation is a single module run to process data or check for new data. A trigger runs once per check, however many bundles it returns. An action runs once per bundle, so five emails are five operations. Bundles earlier in the scenario multiply later modules. The checkmark in the white bubble is the operation count. The coin is the credits. Accessed 2026-10-01.
Why does Make use both words?
Make’s Help Center hub: operations count the activities in a scenario, and credits are what you pay for those activities. The credits page says the words are separate on purpose. The pricing page says that as of August 27, credits are the billing unit, and its usage-allowance header still says “per 10k operations licensed per month” beside “for every 10,000 credits.” The live scorecard’s Make pricing line still says operations per month, dated 2026-09-07. This page does not edit that cell.
When is 1 operation not 1 credit?
The default is 1 operation equals 1 credit. It is not the default when a module is tagged above 1 credit per operation (the credits page shows an example of 2 or 10), when usage is dynamic (tokens, file size, pages, or run time), or when Make Code bills 2 credits per 1 second on Core, Pro, Teams, and Enterprise. Make’s AI Provider bills tokens and operations. Those token tables are on the credits page and on How AI steps change the meter. This page does not reprint them.
What happens when the credits run out?
Make’s pricing FAQ: scenarios will not continue until credits are added. Make notifies you at 75% and again at 90% of purchased credits. You can upgrade, buy extra credits in bundles of 1,000 or 10,000 at the fixed price defined in your subscription, or turn on auto-purchasing of 10,000 credits on Core, Pro, and Teams. The dollar of that fixed price is not printed in the FAQ text read 2026-10-01: —. Credits expire at the end of the term. The cross-tool ceiling is on When you hit the meter.
Does this page change the Make vs n8n vs Zapier scores?
No. Totals are not published yet. It does not edit the pricing cell.
Does this page turn the words into a monthly dollar?
No. This page stays on the two words, as printed on Make’s pricing page and Help Center, accessed 2026-10-01. A fixed monthly dollar from that pricing text: —. It does not invent an extra-credit dollar or annual savings. It publishes no annual savings. Free’s published credit quota on that page is 1,000 credits per month. The rest of the free-plan read is on When free isn’t enough.
Will a commission change these words?
No. Make is a live partner signup (pc=stackscorecard). This page does not add an n8n or Zapier affiliate ID. Commissions do not move a score, a weight, or a pricing cell.
Where should I go next?
For the three-tool dictionary, see Tasks vs credits vs executions. For one job at 50, 500, and 5,000 runs, see Same job, three meters. For the ceiling, see When you hit the meter. For an AI or agent step, see How AI steps change the meter. If Make is the product question, see When Make is the right pick. If you are still on free, see When free isn’t enough. If you already run Zapier or n8n Cloud, see the switching guides. Totals are not published yet.
Affiliate disclosure
Make is a live partner signup (pc=stackscorecard) and is marked affiliate; we may earn a commission. Rankings are not sold. This page does not add an n8n or Zapier affiliate ID (Affiliate disclosure · Disclosures).