Make.com pricing: plans, credits, and three worked scenarios

How to read the Make price list

Make sells two things at once: a feature level (Free, Core, Pro, Teams, Enterprise) and a monthly volume of credits. Each paid plan comes in levels: from 10,000 to 300,000 credits a month for Core, up to 8,000,000 for Pro and Teams. Above that, only Enterprise, with custom pricing, is offered.

The paid entry point is Core: $16 per month for 10,000 credits, or $11 per month billed annually. Compared with the free plan, Core lifts the two limits that get in the way most: active scenarios become unlimited and the minimum interval drops from 15 minutes to 1 minute.

At equal volume, Pro costs more than Core because it adds features (priority execution, custom variables, full-text search in the logs), not credits. The volume levels show it: Core at 20,000 credits is listed at the same price as Pro at 10,000. On the same budget, you are choosing between twice the credits and more features.

Monthly or annual billing

Annual billing costs less, but it also changes how credits get used:

• Core, billed annually: credits reset every month;
• Pro and Teams, billed annually: credits can be used over 12 months, which absorbs one month that is busier than the others.

Either way, unused credits expire at the end of the term.

The catch: the trigger uses credits even when nothing happens

A scheduled scenario checks at a regular interval whether there is anything new. Every check uses 1 credit, whether it finds something or not. Over a 30-day month:

How often it checks	Math	Credits used by the trigger alone
Every hour	24 × 30	720
Every 15 minutes	96 × 30	2,880
Every 5 minutes	288 × 30	8,640
Every minute	1,440 × 30	43,200

What follows directly. The free plan includes 1,000 credits and sets a minimum interval of 15 minutes: a single scenario set to that interval goes past it without processing anything. On Core, a scenario that checks every minute fits neither the 10,000-credit level nor the 40,000 one: it takes the 80,000 level.

Two ways around it: space out the checks, or use a webhook trigger when the app offers one. The scenario then runs only when an event arrives. See the guide what is a webhook?.

Three scenarios, counted in credits

The method: count the modules in each scenario, the trigger included, multiply by the number of runs, then add the empty checks.

Scenario	Math	Credits per month	Plan that covers it
Web form to CRM, by webhook: 4 modules, 200 submissions	200 × 4	800	Free
The same, checking every 15 minutes instead of using a webhook	2,880 + 200 × 3	3,480	Core, 10,000 level
Online store: 1,500 orders by webhook (6 modules), plus an inventory check every 5 minutes (300 updates, 2 actions each)	1,500 × 6 + 8,640 + 300 × 2	18,240	Core, 20,000 level

Between the first and second rows, the useful work is identical: 200 submissions handled. Only the way the scenario starts changes, and usage is multiplied by more than four. In the third, nearly half the credits go to inventory checks.

The cost calculator reruns this math with your numbers and compares it with other tools.

What uses credits when you don’t expect it

• Bundles. An action module uses 1 credit per “bundle” processed. A daily scenario whose trigger returns 100 rows, followed by 2 actions per row, uses 1 + 200 = 201 credits per run, or 6,030 a month.
• Code. “Make Code” uses 2 credits per second of execution, on paid plans.
• AI agents. With Make’s AI provider, an agent uses 1 credit per operation, plus credits based on the tokens used: usage then depends on how long the exchanges are.

On the other side, routers, filters and error handlers use nothing. The full rule is in the Make help center page on credit usage (accessed November 11, 2026).

Beyond the quota

Without credits, scenarios stop until credits are added. Incoming webhooks are queued, within the available storage.

On paid plans, you can buy extra credits by hand, in units of 1,000, or turn on automatic purchases in units of 10,000 (Core, Pro, Teams), capped at the number of credits in your subscription. Every extra credit costs the credit price of your plan plus 25%, so a credit bought as overage always costs more than a credit in the subscription. The Enterprise plan includes “Credits overage protection”, which keeps scenarios running once the limit is reached.

On the entry price, the vendor’s pages contradict each other: the example on the help page about extra credits mentions, for 10,000 credits, a cheaper subscription than the one on the pricing page. The prices shown here are those of the pricing page.

How it compares with n8n and Zapier

The three tools do not count the same thing: credits per module run at Make, workflow executions at n8n, tasks per successful action at Zapier. The head-to-heads do the math side by side: n8n vs Make, Make vs Zapier and n8n vs Zapier.

For everything else (data hosting, AI, limits of the free plan), see the Make profile.