Make credits: calculate usage before choosing a plan

A 15-minute polling schedule can use 2,880 credits in 30 days before any actions. Calculate checks, bundles and module rates before choosing a Make plan.

About this guide

Published by StackOnSale. Publisher: Emmanuel Grenier. Guide updated: 2026-09-25.

Research based on official vendor pages, not a hands-on review.

StackOnSale may earn a commission through disclosed affiliate links on the site. This does not decide which tool fits your needs.

The short answer

Count the schedule first: a trigger that checks every 15 minutes for 30 days makes 2,880 checks, which is 2,880 credits at one credit per check, before any action runs. Most standard modules use one credit per operation, but some are free and others cost more.

Extra credits cost 25% more than included ones. Core credits reset every month, even on annual billing, while annual Pro and Teams plans get a yearly pool. When credits run out, Make's credits page lists three options: upgrade, buy extra credits or turn on auto-purchasing; on October 28, 2026 it no longer says in so many words that scenarios stop. Make's pricing page FAQ still does: read on November 11, 2026, it says your scenarios won't continue to run until credits are added again, with incoming webhooks queued up to your queue storage. The two Make pages word this differently.

Start with the schedule, not the number of boxes

A workflow can use credits even when it finds nothing new. If a standard one-credit polling trigger checks every 15 minutes, around the clock for 30 days, it makes 2,880 checks. That is 30 × 24 × 4, assuming every scheduled check actually runs. Downstream work is not included.

This is a planning example, not a measured customer result. A paused scenario, limited schedule or exhausted credit allowance changes the number of completed checks. A webhook is a different trigger and should not be estimated with this polling formula.

We reviewed the official documentation linked below on September 25, 2026. We have not tested these scenarios ourselves. StackOnSale may earn a commission through the disclosed affiliate link on our Make offer page. The calculation should help you judge fit, not push you into a higher plan.

Count checks, then count the work each item creates

For standard modules priced at one credit per operation, separate scheduled checks from downstream executions. Make's Google Forms example has one check followed by three actions for each response. Ten responses produce 1 + (10 × 3) = 31 operations. At that standard rate, they use 31 credits.

This is not a universal rule for every first module or every workflow. Different module rates, repeated routes, retries, filters, aggregation and AI features can change the result. List the modules that actually run and check their rates.

For a second hypothetical example, assume 1,000 items each reach exactly four one-credit actions during the month. Those actions add 4,000 credits. With the 15-minute polling schedule above, the estimate becomes 2,880 + 4,000 = 6,880 credits. It excludes any other operations, AI usage and separate provider fees.

The table below isolates polling only. All three rows assume 30 days, 24-hour operation, a one-credit check and every scheduled check completing. Choose a frequency that meets your response-time requirement; an hourly check is not a substitute when a customer needs an immediate response.

Polling-only example: 30 days, one credit per completed check
Check interval	Checks per day	Credits over 30 days
15 minutes	96	2,880
30 minutes	48	1,440
60 minutes	24	720

Our arithmetic from Make's documented polling rule, checked September 25, 2026. Assumes every scheduled check runs for 30 full days, at one credit each. Excludes downstream actions, retries and other usage. This is not measured account usage.

A credit is not always one operation

Operations describe module executions; credits are the billing units. Most standard modules consume one credit per operation. Some modules have higher fixed rates or usage-based pricing. Make Code, for example, has runtime-based pricing rather than the standard one-credit rule.

AI billing also depends on the feature and connection. With some custom provider connections, Make bills operations while the AI provider separately bills tokens. Other connections include token or other usage charges in Make credits. Do not assume every AI module follows the same rule.

Make publishes feature-specific rates and credit rules. Read the module documentation and its credit-usage tag, then compare the estimate with the credits recorded in Scenario History. We do not assign an unverified rate to an iterator, aggregator or retry in your workflow.

Reduce unnecessary work without changing the result you need

Where an integration supports instant webhooks, they can avoid periodic checks that find no new data. Processing incoming events and running downstream modules can still consume credits. Whether this saves much depends on how often events arrive and how frequently you would otherwise poll.

Routers and filters do not consume credits themselves. Placing a suitable filter before an unnecessary action can also prevent that action from running. Check that the filter does not discard records you need.

Make's aggregation example reduces a run from 11 operations to 3 by sending one combined email instead of ten separate emails. That changes the output. It is useful only if one combined message meets the requirement.

Make lists the Rollback, Break, Resume, Commit and Ignore error-handler directives as zero-credit modules. That does not make an entire error-handling route free: additional actions and repeated work can still use credits.

Measure a quiet run and a busy run

Start with fictional or non-sensitive sample data. Record one run with no new items, one typical batch and one busy batch. Include any route that may execute after an error. These are suggested checks, not results we have measured.

In Make, open the scenario's History tab and inspect an individual run. Compare operations with credits rather than assuming the two totals match. The scenario builder's credit-usage view can show which modules account for the difference.

Write down your schedule, expected monthly items, actions per item, special module rates and separate provider charges. Repeat the estimate for a busier month. Use those estimates to compare capacity options, without assuming that a larger plan is automatically the better choice.

Check the billing period as well as the allowance

Use Make's official pricing page and your account's selected tier for a current quote. This guide does not present the different prices we observed in September as a price guaranteed for every visitor. Confirm currency, billing period, credit volume and the amount charged upfront.

Annual Pro and Teams subscriptions provide a pool of credits to use during the subscription year. Make's subscriptions page, read on October 28, 2026, does not say when unused pool credits expire; it only says extra credits expire at each monthly reset. Make's pricing page FAQ, read on November 11, 2026, answers both differently: credits expire at the end of the term, and extra credits expire after one month on a monthly subscription or at the end of one year on an annual Pro or Teams subscription. The two pages disagree on extra credits for annual Pro and Teams; check the expiry shown at checkout. Core credits reset monthly, even with annual billing. A monthly allowance and an annual pool are different budgeting constraints.

Extra credits cost 25% more than credits included in the plan, whether bought manually or through auto-purchasing. Check the displayed charge and expiry before buying. You may be better served by changing an unnecessary schedule, changing the credit tier or staying with your existing setup.

Decide after you can explain the estimate

Before choosing a plan, you should be able to explain where your credits will go: scheduled checks, work per item, special module rates and any repeated processing. The useful number is the workload you need, not the number of boxes on the canvas.

Our Make offer page links separately to the official evidence and the disclosed commercial destination. No exclusive discount is claimed here. If you are comparing tools, use the same workload and response-time requirement for each, then read how each vendor counts usage.

Questions

What is the difference between an operation and a credit?

An operation is a module execution that processes or checks data. Credits are Make's billing units. Most standard modules use one credit per operation, but some are free and others have higher fixed or variable rates. Check the feature and connection, including AI and Make Code.

How many credits does checking every 15 minutes use?

Over 30 days, checking every 15 minutes around the clock produces 2,880 scheduled checks. If every check actually runs and the trigger uses one credit per check, that consumes 2,880 credits, even when no new data is found. This excludes all downstream actions.

What happens if I run out of credits?

Make's help pages, read on October 28, 2026, list three options: upgrade, buy extra credits or turn on auto-purchasing, which buys 10,000 credits at a time up to your plan's credit amount per billing cycle. If that payment fails, Make says your scenarios pause until you update your payment method. The usage-email thresholds (90% and 100% to owners and admins) that this guide cited in September no longer appear on Make's credit-tracking page as of October 28, 2026; check your notification settings in your account.

Do extra credits cost more?

Yes. Extra credits cost 25% more than credits included in your plan. The same surcharge applies to manual purchases and auto-purchasing. Check your account for the amount you would pay and when those credits expire.

Do unused credits roll over?

Annual Pro and Teams subscriptions provide an annual pool that you can use during the subscription year. Make's subscriptions page does not say when unused pool credits expire (read October 28, 2026). Core credits reset monthly, even with annual billing. Monthly subscriptions have monthly allocations.

Related offers

Sources

Search, saved offers and price alerts need JavaScript.