Guide · what to watch
How to meter automation — usage, volume, and credits
Watch the meter first. Totals are not published yet. Self-hosted is a separate lane. A score is not a monthly bill. This page does not add new scores.
Meter this job, or don’t meter that way
Meter
Meter if…
You can name the job and count expected runs in the vendor’s own unit — Zapier tasks, Make credits, or n8n executions. You will check what multiplies that count: loops, retries, and polls. Someone looks at usage before the cycle ends, not after a surprise invoice.
Don’t
Don’t meter that way if…
You treat one task as one credit as one execution, guess a monthly dollar from a /500 score, or skip loops, retries, and polls. If you still need to know whether the job is worth automating, stop and open What’s worth automating. That is a process problem, not a unit problem.
A meter-or-don’t check for one job.
- You want to know what to watch on the meter — usage, volume, credits — not which tool.
- You will count in the vendor’s unit and include loops, retries, and polls.
Read more
What this page tells you. Help a small team meter automation — usage, volume, and credits — so you know what to watch before you treat a number as a bill. Count in the vendor’s unit. Include what multiplies the count. This page does not rank tools, does not reprint the four-question flowchart, and it adds no score cells. Dated list prices live on Which automation tool for small teams after you can count.
GuideSome scores not shown yetVendor pages accessed 2026-09-17Live scorecard
This page is not a tool pick
The question here is what to watch on the meter. Whether the process is ready lives on What’s worth automating. Which product to use lives on Which automation tool for small teams. When a named product is already the job, use When Make is the right pick, When Zapier is still the right pick, or When n8n self-host is worth it. When a run fails, name the class on When automations fail and the product lane on Error handling across Make, n8n, and Zapier. This page does not reprint those reads. It does not rank tools. It does not add new scores.
The dictionary of the three words — what a task, a credit, and an execution count, and what they do not — is Tasks vs credits vs executions. This page does not reprint that dictionary. It is what to watch after you know the words.
This page also skips a list-price table. Make’s credit slider is not a fixed dollar here. The question is what to watch — not which plan to buy. After you can count, dated official list prices live on the picker. This page does not claim you will save money, and it does not invent a monthly dollar from a /500 score.
Four things to watch
Usage, volume, cost, and the vendor’s unit are different jobs. Watch them in that order. This is not a 1–5 score.
Swipe sideways on a narrow screen. Not a scored table.
| Watch | What it means | Do this | Don’t do this |
|---|---|---|---|
| Usage | How many units this job already used in the current cycle. | Open the vendor’s usage view and name the job that spent them. | Treat last month’s leftover as a reason to add more flows. |
| Volume | How often the job will run — weekly, daily, or hourly. | Write runs × steps in the vendor’s unit before you pick a plan. | Guess volume from a /500 score, or say “this should save time.” |
| Cost | The plan you already pay, in the currency the vendor prints. | Compare your unit estimate to a dated official list after you can count. | Turn a unit count into a monthly dollar, or claim you will save. |
| Credits / units | The vendor’s actual meter — Zapier task, Make credit, or n8n execution. | Count loops, retries, and polls in that unit. | Treat one task as one credit as one execution. |
Count in the vendor’s unit
Each vendor meters a different thing. Compare the job in that unit first. Do not treat one task as one credit as one execution. Dated quotes below are from primary vendor pages, accessed 2026-09-17.
Task
Zapier
A task is any successful action that runs in Zapier. Only successful actions count toward your task usage.
Triggers, Filter, Paths, Formatter, Delay, and Looping do not count. Polls never use tasks. A successful action after a found event still does.
Credit
Make
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.
By default, 1 operation equals 1 credit. A trigger check is 1 operation. Token-based AI modules are dynamic. Listed error handlers do not consume operations. Verify the module you actually run.
Execution
n8n
An execution is a single run of a workflow.
Paid-plan quota counts production runs. Manual tests, sub-workflow runs, and error-workflow runs do not add a quota execution.
Zapier’s task-usage article also names Code, Lead Router, and MCP as different task rates. Make’s credits guide names token-based AI modules as dynamic. Those are not the sanity-check job below. How AI and agent steps change each meter lives on How AI steps change the meter. Verify the module you actually run.
What multiplies the meter
A surprise invoice is usually a unit surprise, not a hidden list price. Iterators, retries, and polling change how many units a job uses. This table stays in units. It does not invent an overage dollar.
Swipe sideways on a narrow screen. Not a scored table.
| What multiplies | Zapier | Make | n8n |
|---|---|---|---|
| Iterator / loop | The Looping step is 0 tasks. Each successful action after the loop is 1 task per iteration — 500 loops of one action is 500 tasks. | An iterator turns an array into one bundle per item. Later modules run once per bundle. One operation is 1 credit by default. | Loop Over Items stays inside one workflow run. Quota still counts one production execution for that run. |
| Retry / replay | A full Zap replay is a new run. Successful steps count again, even if they already counted. Errored or halted steps do not count. Autoreplay retries Errored runs, not a Safely halted search. | When an error handler activates, it does not consume operations. Later module actions on a retry still count as operations. | An error workflow does not add a quota execution. A new production run is a new execution. |
| Polling / schedule | Polling triggers never use tasks, even at a two-minute interval. Tasks start only when a successful action runs after a found event. | A trigger check is 1 operation no matter how many bundles it returns. Later modules multiply by that bundle count. | A Schedule trigger counts one execution every time it fires. A polling trigger counts only when it finds new data. Empty polls do not count. |
Sources and access date sit under Sources, accessed 2026-09-17. If a run fails, name the class on When automations fail before you rewrite the flow. Quota or a fatal stop is a different job from a retry.
Same-job sanity check
Lead arrives → write a sheet or CRM row → Slack DM. One trigger and two successful actions. One hundred runs a month. No iterator, no replay, no extra poll in this count.
Swipe sideways on a narrow screen.
| Product | Unit | What counts on this job | 100 runs / month |
|---|---|---|---|
 Zapier | Task | Two successful actions. The trigger does not count. | ~200 tasks |
 Make | Credit | Trigger check plus two module actions. Listed error handlers do not consume operations. | ~300 credits |
 n8n | Execution | One workflow run, regardless of step count. | 100 executions |
Approximate because a retry, a Paths branch, or an extra module changes the Zapier or Make count. n8n still bills one execution per run. The same two writes are not the same number on each meter — that is the point. Do not copy the interactive volume ladder here — the 5-step job at 50 / 500 / 5,000 runs lives on Same job, three meters.
Don’t turn a unit into a bill
A unit count is not a monthly dollar. A /500 score is not a plan. This page does not invent an overage dollar or a converted list. It publishes no annual savings.
- Stay in units until you can name runs × steps in the vendor’s meter.
- Then open dated list prices on Which automation tool for small teams — not a slider screenshot from memory.
- Verify the module you run. AI token modules on Make, and Code / Lead Router / MCP on Zapier, use different rates than the sanity-check job.
Not tax or billing advice. See editorial standards.
After you can name the meter
You can count the job in the vendor’s unit. Now pick how it runs — without treating this page as a ranking.
- Still deciding if the job is ready: What’s worth automating — and what to leave manual.
- Four questions, then a pick: Which automation tool for small teams.
- When a named product is the job: When Make is the right pick (and when it is not) · When Zapier is still the right pick (and when it is not) · When n8n self-host is worth it (and when it is not).
- The 5-step volume ladder: Same job, three meters — tasks vs credits vs executions.
- When a run fails: When automations fail — name the class first · Error handling across Make, n8n, and Zapier.
- When to pick each: Make vs n8n vs Zapier — when to pick each · live scorecard (totals are not published yet; self-host is a separate lane).
Primary CTA stays the live scorecard. This page does not reprint the picker flowchart.
How this sits on the scorecard
How this sits on the scorecard
The live card is Make vs n8n vs Zapier. Totals are not published yet.
When-to-pick copy lives on Make vs n8n vs Zapier — when to pick each. Longer compares: Make vs n8n · Make vs Zapier · n8n vs Zapier. Scoring rules: How scoring works.
Product links
Sources
Primary vendor unit and multiplier pages. Access date for every citation on this page: 2026-09-17. This page does not publish list prices. We do not invent search volumes, testimonials, or a converted list.
- Zapier — how task usage is measured · accessed 2026-09-17
- Zapier — understanding Looping by Zapier · accessed 2026-09-17
- Zapier — replay Zap runs · accessed 2026-09-17
- Make — credits · accessed 2026-09-17
- Make — operations · accessed 2026-09-17
- Make — iterator · accessed 2026-09-17
- Make — overview of error handling · accessed 2026-09-17
- n8n — understand executions · accessed 2026-09-17
- n8n — Loop Over Items · accessed 2026-09-17
FAQ
What should I watch when I meter an automation?
Four things: usage already spent this cycle, volume you can count, the plan you already pay, and the vendor’s actual unit — a Zapier task, a Make credit, or an n8n execution. Meter if you can name the job and watch those in the vendor’s unit. Do not treat one task as one credit as one execution.
What is a Zapier task versus a Make credit versus an n8n execution?
A Zapier task is a successful action step. Triggers, Filters, Paths, Formatter, Delay, and Looping do not count. A Make credit is usually one module action; by default 1 operation equals 1 credit. A trigger check is 1 operation. Listed error handlers do not consume operations. An n8n execution is one workflow run. Step count does not multiply the execution. The plain dictionary — what each word counts and what it does not — is Tasks vs credits vs executions. This page is the watch list, not that dictionary.
How does the same small-team job meter on each tool?
Lead arrives → write a sheet or CRM row → Slack DM: one trigger and two successful actions. At 100 runs a month that is about 200 Zapier tasks, about 300 Make credits (the trigger check plus two module actions), and 100 n8n executions. That is unit math, not a score. For a 5-step job with a volume ladder, see Same job, three meters.
What multiplies the meter — iterators, retries, or polling?
Zapier: polls are 0 tasks; a loop’s later actions are 1 task each; a full replay recounts successful steps. Make: a trigger check is 1 operation; later modules run once per bundle, so an iterator multiplies credits. n8n: a schedule fires one execution every time; a polling trigger counts only when it finds data; Loop Over Items stays one execution. This page does not invent an overage dollar.
Does this page publish a monthly bill or a list-price table?
No. This is a process check. It skips a list-price table. Make’s credit slider is not a fixed dollar on this page. Dated official list prices live on Which automation tool for small teams after you can count. This page does not invent a monthly dollar or an overage dollar. It publishes no annual savings.
Does this page decide if the job is worth automating, or which tool to pick?
No. Pass or defer the job on What’s worth automating. Pick a product on Which automation tool for small teams. When a named product is already the job, use When Make is the right pick, When Zapier is still the right pick, or When n8n self-host is worth it. This page only tells you what to watch on the meter.
Does this guide change the Make vs n8n vs Zapier scores?
No. Totals are not published yet.
Affiliate disclosure
Make Partner (pc=stackscorecard) is live elsewhere on the site and is not linked from this page. n8n and Zapier stay official-site URLs with UTM only — no invented IDs. Zapier has no Stack affiliate. Rankings are not sold. Policy: Affiliate disclosure · Disclosures.