Make.com Pricing 2026: Credits, Core, Pro & Teams Explained

Make’s plan names are the small half of the pricing decision. The number that sets your bill is the credit slider — and one automation run rarely costs one credit.

Updated August 20268 min read

💰 Quick Pricing Summary

Free: $0 — 1,000 credits/month, full visual builder, 3,000+ apps, 15-minute minimum interval between runs. Core: $12/month at 10,000 credits — unlimited active scenarios, minute-level scheduling, API access. Pro: $21/month at 10,000 credits — priority execution, custom variables, full-text log search. Teams: $38/month at 10,000 credits — teams, roles and shared templates. Enterprise: custom.

Every paid price above is quoted at the default 10,000 credits a month. The slider runs to 8 million+, and the price rises with it — so “how much is Core?” has no single answer. Annual billing advertises savings of 15% or more.

🔍

Metered cloud, or self-hosted and unmetered?

Credit-based pricing rewards low-volume, high-value automations and punishes chatty ones. If your workflows fire constantly, the honest comparison is against a self-hostable engine where volume is free and your time is the cost.

n8n Pricing

If high volume makes per-operation billing hurt

Linear Pricing

The most common destination for Make's output

Make Plans Compared (at 10,000 credits/month)

Feature	Free	Core	Pro	Teams
Price	$0	$12/mo	$21/mo	$38/mo
Included Credits	1,000/mo	10,000/mo	10,000/mo	10,000/mo
Active Scenarios	Limited	Unlimited	Unlimited	Unlimited
Minimum Run Interval	15 minutes	1 minute	1 minute	1 minute
App Connectors	3,000+	3,000+	3,000+	3,000+
Make API Access	No	Yes	Yes	Yes
Priority Execution	No	No	Yes	Yes
Custom Variables	No	No	Yes	Yes
Full-Text Execution Log Search	No	No	Yes	Yes
Teams & Team Roles	No	No	No	Yes
Shared Scenario Templates	No	No	No	Yes
Maia, AI Agents & MCP Server	Yes	Yes	Yes	Yes
Overage Protection	No	No	No	Enterprise

Prices read from Make's pricing page in August 2026 at the default 10,000 credits/month position on the slider. Every paid figure moves as you increase the credit tier, and Make advertises 15%+ savings on annual billing — check both toggles on make.com/en/pricing against your own credit forecast before subscribing.

How Credits Actually Get Spent

One credit is one module action. The mistake almost everyone makes when forecasting is to count scenario runs instead of module executions — which understates consumption by however many steps the scenario has.

A simple 3-module scenario

Trigger, transform, write. Roughly 3 credits per run. Fired hourly, that is about 2,160 credits a month — comfortably inside a 10,000-credit Core plan with room for several more automations.

A 10-module scenario with a router

Roughly 10 credits per run, more if an iterator loops over records. Fired 100 times a day, that is about 30,000 credits a month — three times the default tier, and you have built exactly one workflow.

Custom code

The Make Code App bills 2 credits per second of execution time rather than per action. A slow API call inside a code step is charged by the clock, which makes efficient code a direct line item on the invoice.

These are worked illustrations of Make's published rule — one credit per module action, 2 credits per second of code execution — not quoted figures from Make.

Understanding Each Plan

Free — $0, 1,000 credits/month

No time limit, and the full visual builder. It exists to answer one question: can you model your workflow in Make's scenario editor at all?

What you get:

1,000 credits a month — roughly 100 runs of a 10-module scenario
The full no-code drag-and-drop builder
3,000+ app connectors, routers and filters
Maia, the AI Toolkit and MCP server access
Customer support

What you don't get:

Runs more often than every 15 minutes
Unlimited active scenarios
The Make API

Core — $12/month at 10,000 credits

The tier most solo operators live on, and the one that removes the two limits that actually block real work: scenario count and the 15-minute floor.

Worth it when:

You have more than a couple of automations running at once
Something needs to react in under fifteen minutes
You want to drive Make from your own code via the API
Data transfer limits on Free have started biting

Skip it when:

One nightly scenario is genuinely all you run
Latency matters — that is a Pro-tier concern

Pro — $21/month at 10,000 credits

Nine dollars more for three things, one of which is not really a feature at all: your scenarios stop queueing behind everyone else's.

Priority scenario execution — the reliability upgrade disguised as a perk
Custom variables, so credentials and constants live in one place
Full-text execution log search — the difference between debugging in minutes and scrolling for an hour
Everything in Core, including API access and minute-level scheduling

Teams — $38/month at 10,000 credits

Not a volume tier. It is the tier where more than one person can safely touch the automations without overwriting each other.

Teams and team roles
Create and share scenario templates across the organisation
Everything in Pro, including priority execution
Still 10,000 credits at the default slider position — collaboration, not capacity

Enterprise — custom

Where the failure modes get handled properly. Overage protection alone justifies the conversation once automations are load-bearing.

Custom functions support and extended code resources
Enterprise app integrations and an on-prem agent for local networks
Overage protection — scenarios do not silently stop
Advanced security features and 24/7 support
Access to Make's Value Engineering team

What the Pricing Page Doesn't Tell You

The plan name is not the price

Every quoted figure assumes 10,000 credits. The slider goes past 8 million, and the same “Core” plan costs wildly different amounts at either end. Any article that tells you Make Core costs a fixed sum has quietly picked a slider position on your behalf.

Failed runs still cost credits

Modules that execute and then error have already consumed their credit. A misconfigured scenario retrying against a rate-limited API is the classic way to discover this — build error handlers early, and not because they are elegant.

Overage protection is Enterprise-only

On Free through Teams, exhausting credits means automations stop. If something customer-facing depends on a scenario, either buy meaningful headroom or accept that your automation has a monthly cliff edge with no warning attached.

AI modules are still modules

Maia, AI Agents and the AI Toolkit are included on every plan, which reads as free. They consume credits like any other module, and if you bring your own LLM key you pay that provider on top. An agentic scenario is the most expensive kind of scenario to run on a credit meter.

Which Make Plan Should You Pick?

Stay on Free if:

You are prototyping and 1,000 credits covers the test runs
Nothing needs to react faster than every fifteen minutes
You are still deciding whether the scenario model fits your head

Choose Core ($12/mo at 10k credits) if:

Several automations run continuously
Minute-level scheduling or the API matters
Your forecast lands well under the credit tier you picked

Choose Pro ($21/mo at 10k credits) if:

Execution latency has real consequences
You debug scenarios often enough to want log search
Shared constants across scenarios have become a maintenance problem

Choose Teams ($38/mo at 10k credits) if:

More than one person builds or maintains scenarios
You want role-based access rather than a shared login
Repeatable patterns should be templates, not copy-paste

Not sure? Build the scenario on Free first and read the actual credit consumption after a week. Multiply by four, add 50% for error retries, and pick the slider tier that covers it. Getting the credit number right saves more money than choosing between Core and Pro ever will.

Frequently Asked Questions

How much does Make.com cost per month?

At the default 10,000 credits a month, Make lists Core at $12, Pro at $21 and Teams at $38 per month, with a free plan at 1,000 credits and custom Enterprise pricing. Those numbers are not fixed: the price scales with the credit slider, which runs from 10,000 all the way past 8 million. Make also advertises savings of 15% or more for paying annually rather than monthly.

What is a Make credit?

Each module action inside a scenario consumes one credit — adding a row to a Google Sheet, fetching Gmail account data, posting to Slack. A single automation run through a ten-module scenario therefore costs around ten credits, not one. This is the number that catches people out: a workflow that fires 100 times a day through a modest scenario can burn a 10,000-credit allowance inside a week.

Is Make.com free?

Yes, with no time limit. The free plan includes 1,000 credits a month, the full no-code visual builder, 3,000+ app connectors, routers and filters, and customer support. The two real constraints are the credit allowance and a 15-minute minimum interval between scenario runs — so anything that needs to react quickly, or run more often than four times an hour, needs a paid plan regardless of volume.

What is the difference between Make Core and Pro?

Core is the first tier with unlimited active scenarios, minute-level scheduling, higher data transfer limits and Make API access. Pro adds priority scenario execution, custom variables and full-text execution log search. The one that quietly matters is priority execution: when the platform is busy, Core scenarios queue behind Pro ones, which turns a pricing decision into a reliability decision for time-sensitive automations.

Is Make cheaper than Zapier?

Usually, and sometimes dramatically — but the comparison is not like-for-like. Zapier historically bills per task, roughly one per action delivered, while Make bills per module operation inside a scenario. Make's per-unit price is far lower, so complex multi-step workflows are much cheaper on Make. The trade is complexity: Make's visual builder gives you routers, iterators and error handlers that Zapier abstracts away, and that power has a learning curve attached.

Do Make's AI features cost extra credits?

The AI capabilities — Maia, the AI Toolkit, AI Agents (beta), AI Web Search and the MCP server — are available across plans, but they run as modules and therefore consume credits like anything else. The Make Code App is billed more aggressively at 2 credits per second of code execution time. If you are running LLM calls through Make with your own provider key, you are also paying that provider separately.

What happens when I run out of Make credits?

Scenarios stop running until the allowance resets or you move up the slider — which is why the credit tier, not the plan name, is the number to get right. Overage protection is an Enterprise feature, so on the self-serve plans the failure mode is silence: automations simply stop. If an automation is load-bearing for your business, set the tier with real headroom rather than trimming to the exact forecast.

Is Make the same as Integromat?

Yes — Integromat rebranded to Make, and the underlying visual scenario builder is the same lineage. Old Integromat tutorials and community answers still largely apply to the modern product, which makes the learning curve gentler than the interface first suggests. Pricing, however, has been restructured around credits, so any cost figure from an Integromat-era article should be treated as out of date.

Related Resources

Make Review 2026

How the visual scenario builder holds up on real automations.

n8n Pricing 2026

The self-hostable alternative when per-operation billing stops working.

Linear Pricing 2026

Where automated intake usually needs to land as tracked work.

Sentry Pricing 2026

Another metered tool where the quota, not the tier, sets the bill.

AI Productivity Tools

Browse every automation and productivity tool we track.

All Tool Pricing

Every pricing breakdown in the catalog, side by side.

Ready to Try Make?

Build your most annoying manual process on the free plan and watch the credit counter for a week. That number — not the plan name — is the one that tells you what Make will cost you.

See Make Plans →

Free gives 1,000 credits a month with no time limit. Core starts at $12/month for 10,000.

ChatGPT already recommends Make. Does it recommend yours?

If you're building in workflow automation, run a free AI-visibility scan on your own product — we ask ChatGPT across 5 prompt angles and score how often you get named. ~30 seconds, no signup, no card.

Scan my tool — free →or scan Make instead

📬 Get the best new AI tools delivered weekly

One concise email with fresh launches, trending picks, and featured standouts.