All free tools

Make.com credits calculator

Add your Make scenarios, choose a polling schedule or an instant trigger, and enter how many items arrive a day and how many modules handle each one. See your typical and busy-month credits, how much of that is spent on empty checks, and which plan size to buy.

Runs in your browser. Nothing you enter is sent to EpiFive or Make unless you choose to email yourself the summary.

Loads the worked example from our Make pricing guide.
  1. Trigger
    Make’s default is 15.
    24 unless you limit the hours.
    Rows, emails, orders… found by the trigger.
    Count the trigger; skip routers and filters (free).
    30 every day, about 22 weekdays.
Up to 10 scenarios.
1.5 = a busy month has 50% more items. 1 = no peak.
Added on top of the peak month.
Typical month4,080 credits
Peak month4,680 creditsitems × 1.5
Polling checks alone2,880 creditscharged even when nothing is found
Plan size with 20% margin5,616 creditsCore
Credits a month per scenario
ScenarioPolling checksProcessing itemsTypical monthPeak month
New sheet rows to email2,880 (96/day)1,2004,0804,680
Plan that fits: Core. Core credit tiers go up to 300,000 credits a month; the smallest paid tier in Make’s examples is 10,000. Your estimate is below the 10,000-credit tier, so that tier leaves room to grow. Plans also differ in features and in the shortest schedule interval they allow, so compare the plan cards on Make’s pricing page. Limits checked 18 November 2026.

Guides that use this tool

How to use it

  1. Add one row per scenario. Give it a name so you can tell the rows apart in the results.
  2. Choose the trigger. Scheduled (polling) is a trigger that checks for new data on a timer, usually a module whose name starts with “Watch”. Instant (webhook) is a trigger with the lightning icon and “instant” tag, which the app calls when something happens.
  3. For polling, enter the minutes between checks and the hours a day the schedule runs (24 unless you restricted it).
  4. Enter how many new items (rows, emails, orders) or events arrive on a normal day.
  5. Enter the modules that run for each item, counting the trigger. Leave out routers, filters and error handlers, which are free. If an iterator makes a module run several times per item, count it that many times.
  6. Enter the days a month the scenario runs: 30 for every day, about 22 for weekdays only.
  7. Optionally set a peak-month multiplier for your busiest month, and a safety margin to size the plan on.

How we calculate

Per scenario, for one active day:

  • Polling trigger: checks a day = schedule hours × 60 ÷ interval. Credits a day = checks a day + items a day × (modules − 1). Each check costs 1 credit whether or not it finds anything; the trigger costs that 1 credit per check however many items the check returns.
  • Instant trigger: credits a day = events a day × modules. Each event starts its own run, and the trigger uses 1 credit per run.
  • Monthly credits = credits a day × active days. Totals are rounded up to whole credits.
  • Peak month: items or events × the multiplier. Polling checks do not change in a busy month, so they are not multiplied. Plan size = peak month × (1 + safety margin).
  • Plan fit uses the credit ceilings Make publishes: Free 1,000 credits a month; Core up to 300,000; Pro up to 8 million; above that, ask Make about Teams or Enterprise. The smallest paid tier in Make’s own examples is 10,000 credits a month.

Rules and limits were checked on 18 November 2026 against Make’s own pages: the Help Center articles How features use credits (triggers use 1 credit per run even when they find no new data; actions use 1 credit per bundle; routers, filters and error handlers are free), Operations, Credits (1 operation = 1 credit for non-AI apps), Types of modules (polling vs instant triggers), Adjustments to plans and pricing (Core and Pro credit ceilings and the 25% extra-credit cost, effective 6 November 2025) and Extra credits, plus the Make pricing page (Free plan 1,000 credits a month, what happens when credits run out).

What we could not verify, so the calculator does not guess:

  • Plan prices and the full list of credit tiers. The plan cards on Make’s pricing page load in the browser and change by region and billing term, so read the price for your tier there.
  • The shortest polling interval for each plan. Make’s scheduling page says it “depends on your plan” without listing values; check the plan card before you design around a short interval.
  • AI modules and the Make Code app, whose credit use varies with tokens, pages or run time.
  • Teams plan credit limits: Make publishes no ceiling for Teams, so the calculator suggests Core or Pro by credits and leaves the feature choice to you.

Worked example

A scenario watches a Google Sheet every 15 minutes, sends an email for each new row and updates a status cell: 3 modules. About 20 rows arrive a day. Checks: 24 × 60 ÷ 15 = 96 a day, 1 credit each. Work: 20 rows × 2 modules after the trigger = 40 credits a day. Total 136 a day, or 4,080 credits in a 30-day month, of which 2,880 are polling checks. That fits Core’s smallest 10,000-credit tier. The same scenario with an instant trigger would use 20 × 3 × 30 = 1,800 credits, and checking every 60 minutes instead of 15 would use 1,920. The “Example” button above loads this scenario.

Before you buy, open the scenario in Make, click Run once with realistic data and turn on credits in the module bubbles. If a module shows more credits than operations, use the real figure per item.

  • Azure pricing calculator: Live Azure list prices for VMs, disks, App Service, SQL, AKS and more in INR or USD, with reservation and spot savings, region comparison and a monthly estimate.
  • Cloud cost optimizer: Upload an Azure or AWS cost export and get explainable savings: reservations, idle disks, dev/test schedules, storage tiers and more. The file never leaves your browser.
  • Cron expression generator: Build or explain a 5-field cron expression in plain English and see the next run times.

Related guides

Questions people ask

Does a Make polling trigger use credits when it finds no new data?

Yes. Make’s Help Center page “How features use credits” says trigger modules use 1 credit per run regardless of whether they return data, and that even when a trigger finds no new data it still uses 1 credit for checking. A scenario that checks every 15 minutes therefore uses 96 credits a day before it processes anything.

How many credits does one Make scenario run use?

One credit for the trigger, plus one credit for every other module each time it runs. Modules after the trigger run once per bundle, so a run that finds 10 new rows and sends an email for each uses 1 credit for the trigger and 10 for the email module. Routers, filters, error handlers and Make Functions modules use no credits.

Is an instant (webhook) trigger always cheaper than polling?

No. An instant trigger only runs when an event arrives, so a quiet scenario saves all the empty checks. But each event starts its own run, and the trigger uses 1 credit per run, so a scenario that receives more events a day than it would make polling checks can cost more with an instant trigger. The calculator shows both figures for each polling scenario.

What happens if I use more credits than my Make plan includes?

Make’s pricing page says scenarios stop running until credits are added, incoming webhooks queue up to your webhook queue allowance, and polling scenarios pick up records from their last successful run. Paid plans can buy extra credits in steps of 1,000 or turn on auto-purchase of 10,000 at a time; since 6 November 2025 extra credits cost 25% more per credit than the credits in your plan.

Does the calculator handle AI modules?

Not exactly. Make bills most apps at 1 credit per operation, but Make AI modules using Make’s AI Provider add credits based on tokens, some AI Content Extractor modules use 2 or 10 credits per operation, and the Make Code app uses 2 credits per second of execution. Run the scenario once with credits shown in the editor and use that number per item instead.

Do unused Make credits roll over?

No. Make’s pricing page says credits expire at the end of the term. Monthly plans get a new allocation each month; on annual Pro and Teams plans the credits for the year are available as one pool, while Core plans keep a monthly allocation even when billed annually.