Make.com Pricing in 2026: Plans, Credits, and Real Costs Explained
Make’s biggest pricing change in 2026 is the rename of its billing unit from “operations” to “credits” — and since most articles still say “operations,” it’s the first thing to get straight. Plans (annual pricing, roughly 15%+ off monthly): Free is $0 (1,000 credits/month, 2 active scenarios); Core is around $12/month (10,000 credits, unlimited scenarios); Pro is around $21/month; Teams is around $38/month; Enterprise is custom. Credits are consumed per module call — every action a scenario takes spends one — so complex, branchy scenarios cost more than the headline price suggests.
This guide covers the plans, how credits actually work, what changed from operations, how to estimate your cost, how it stacks up against Zapier, and when Make’s pricing starts to bite.
The plans (2026)
All figures are approximate and as of 2026; Make adjusts pricing periodically, and annual billing runs roughly 15%+ cheaper than monthly. The 10,000-credit tier is the common reference point.
| Plan | Price (annual, approx) | Credits/mo | Scenarios | Min interval | Notable |
|---|---|---|---|---|---|
| Free | $0 | 1,000 | 2 active | 15 min | Try it, low volume |
| Core | ~$12/mo | 10,000 | Unlimited | 1 min | Best entry value |
| Pro | ~$21/mo | 10,000+ | Unlimited | 1 min | Priority execution, custom variables, full-text log search |
| Teams | ~$38/mo | 10,000+ | Unlimited | 1 min | Multi-user, roles/permissions |
| Enterprise | Custom | Custom | Unlimited | 1 min | SSO, advanced security, SLAs |
Higher credit allotments are available within each paid tier — you scale the credit pack up as your volume grows, which is the main lever on your monthly bill.
How credits actually work
A credit is consumed per module call inside a scenario. A module is a single step — fetch a record, send a message, parse data, route a branch. So the cost of a scenario isn’t “one credit per run”; it’s one credit per module that executes per run.
Two things make this add up:
- Module count. A scenario that watches for a new email, parses it, looks up a customer, creates a CRM record, and sends a Slack message is five modules — roughly five credits every time it runs.
- Iterators and routers. If a module loops over a 20-item array, that’s 20 executions. Routers that fan out into multiple branches execute the modules in each active branch. Complex logic is exactly where credit usage multiplies.
Make AI Agents (shipped February 11, 2026, across all plans) also consume credits as they call modules, so agentic scenarios should be budgeted like any other multi-module flow.
Operations vs credits: what changed
Historically Make billed in operations — and the practical accounting was similar (per module call). The 2026 shift to credits unifies the metering language and how add-on consumption (including AI features) is counted, but the core mental model is unchanged: you pay per module call.
Why it matters in practice: nearly all existing tutorials, Reddit threads, and comparison posts say “operations.” If you’re reading older guidance, mentally substitute “credits” — the math of “every step costs” still holds, and that’s the number to plan around.
How to estimate your cost
A quick back-of-envelope method:
- Count modules in each scenario (every step, including the trigger).
- Estimate runs per month for that scenario.
- Multiply, then add an iterator/router fudge factor. modules × runs = base credits; bump it up if you loop over arrays or branch.
- Sum across all scenarios. That total tells you which credit pack you need.
Example: a 5-module lead scenario that fires 40 times a day ≈ 5 × 40 × 30 = 6,000 credits/month — comfortably inside Core’s 10,000. Add a second scenario that iterates over line items and you can cross 10,000 quickly. The lesson: it’s not your number of scenarios that drives cost, it’s modules × frequency × iteration.
How it compares to Zapier
Zapier bills per task (per action step), starting around $19.99/month for 750 tasks (annual), with per-task overage. Make bills per credit (per module call), starting around $12/month for 10,000 credits with unlimited scenarios. For the same multi-step work, Make is usually cheaper per unit and far more generous on volume at the entry tier — which is why it’s a common cost-driven switch. The flip side: Zapier has 8,000+ integrations to Make’s ~3,000+, and a gentler learning curve. Full breakdown in Zapier vs Make.
When Make’s pricing bites
Make is cheap until your scenarios get heavy. The credit model punishes complexity, so costs climb when you:
- run scenarios with many modules at high frequency,
- iterate over large arrays (each item is an execution),
- fan out into multiple router branches,
- lean heavily on AI Agents or other credit-consuming add-ons.
At that point you’re either upsizing your credit pack repeatedly or refactoring scenarios to shave modules — both of which are your job, because Make makes you the builder and the maintainer. If credit math and constant tuning aren’t how you want to spend your time, the alternatives are worth a look — see Make alternatives.
If you’d rather not meter or build at all
There’s a category that skips the metering question entirely for the judgment-heavy work. Carly is an AI executive assistant for non-technical people: you describe the outcome in plain English and Carly builds and runs the workflow for you — in Gmail and Outlook, on triggers, 24/7 — across 200+ integrations. On cost, every step that doesn’t use AI runs free, unlimited — no credit counter on the deterministic plumbing — with AI agents from $35/month.
To be fair to Make: for deterministic multi-app plumbing with heavy branching, a visual builder is the right tool, and Make does it cheaply and powerfully. Carly’s lane is the inbox-and-calendar judgment work — reading, deciding, replying, filing, updating the CRM — where you don’t want to count credits or be the one maintaining the scenario.
Frequently Asked Questions
How much does Make.com cost in 2026?
Make’s Free plan is $0 (1,000 credits/month, 2 scenarios). Core is around $12/month (10,000 credits, unlimited scenarios), Pro around $21/month, and Teams around $38/month, with Enterprise custom — all annual pricing, roughly 15%+ cheaper than monthly. You scale the credit pack up as volume grows.
What’s the difference between Make operations and credits?
Make renamed its billing unit from “operations” to “credits” in 2026. The accounting is essentially the same — you’re charged per module call — but most older articles still say “operations.” When you read them, substitute “credits.”
How are Make credits consumed?
One credit per module call in a scenario. A five-step scenario spends about five credits per run, and iterators (looping over arrays) and routers (branching) multiply usage because each iteration and active branch executes modules.
Is Make cheaper than Zapier?
Usually, per unit of work. Make’s Core is around $12/month for 10,000 credits with unlimited scenarios, versus Zapier’s per-task model from around $19.99/month for 750 tasks. Zapier wins on integration breadth and simplicity; Make wins on cost and branching power. See Zapier vs Make.
Does Make have a free plan?
Yes — $0/month for 1,000 credits and 2 active scenarios, with a 15-minute minimum interval between runs. It’s enough to test simple automations; you’ll outgrow it quickly at any real volume.
How do I avoid running out of Make credits?
Reduce modules per scenario, avoid unnecessary iterators on large arrays, consolidate router branches, and right-size your credit pack. If constant tuning isn’t worth your time, consider an AI assistant like Carly, where non-AI steps run free, unlimited.
More: Make alternatives · Zapier vs Make · Best AI workflow automation tools
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
