Make.com pricing: plans, credits and what you really pay

For US buyers, Make’s paid plans start at $12 a month billed yearly ($16 billed monthly) for the Core plan with 10,000 credits. Pro is $21 and Teams $38 a month billed yearly at the same 10,000 credits, and the Free plan gives 1,000 credits a month. Those are the US prices in AskGPU’s data, checked October 18, 2026. What you actually pay depends on how many credits your scenarios burn, and two rules decide that: every trigger check costs a credit even when it finds nothing, and extra credits cost 25% more than plan credits.

How this guide was put together: plan prices come from AskGPU’s price data for Make, read from Make’s pricing page with its US country setting on October 18, 2026. Make’s pricing page loads its prices with JavaScript, so on November 9, 2026 we could read its text (allowances, FAQ, payment terms) but not the price figures. The credit, billing, upgrade and cancellation rules come from Make’s help center, read November 9, 2026. Zapier’s tiers come from its pricing page, read the same day. We haven’t run these scenarios on Make ourselves; the worked examples are arithmetic on the published rules.

How much does Make cost per month?

Make sells four self-serve plans and a sales-led Enterprise plan. Every self-serve plan starts at 10,000 credits a month, and the price rises as you move the credit slider up.

Plan	Billed yearly (per month)	Billed monthly	Credits at the entry tier	What it adds
Free	$0	$0	1,000 a month	Routers and filters; 15-minute minimum run interval
Core	$12	$16	10,000 a month	Unlimited active scenarios; scheduling down to the minute
Pro	$21	See our Make page	10,000 a month	Annual plans get the year’s credits up front (below)
Teams	$38	See our Make page	10,000 a month	Teams and team roles
Enterprise	Custom	Custom	Custom	Custom functions, 24/7 enterprise support, overage protection, advanced security

US prices, as of October 18, 2026. Pro and Teams monthly-billing prices aren’t in our data, so we don’t quote them.

Over a year at the entry tier, that’s:

• Core billed yearly: 12 × $12 = $144. Billed monthly: 12 × $16 = $192. Paying yearly saves $48, a quarter of the monthly price.
• Pro billed yearly: 12 × $21 = $252.
• Teams billed yearly: 12 × $38 = $456.

Make’s pricing page also advertises a Start-up Plan: “Under 20 employees? Check if you qualify for our Start-up Plan and get 50% off Business.” The page doesn’t list a Business price, so we can’t put a figure on it. Nonprofits are told to contact Make.

Why do other sites say Core costs $9?

Make shows different plans and prices depending on the visitor’s country, all in US dollars. When AskGPU checked on October 18, 2026, visitors from the UK, Germany and Canada saw Core at $9 a month billed yearly, US visitors saw $12, and visitors from India saw a single “Make Plan”. Several top search results quote the $9, $16 and $29 figures, and Google’s own summary mixes both sets. If you’re billed as a US customer, plan on $12, $21 and $38. Make’s own help-center example of the extra-credit formula also uses a “$9 plan”, which is the non-US Core price.

What is a Make credit, and how many does a scenario use?

Make’s pricing FAQ says credits have been its billing unit since August 27. Make says most non-AI modules use 1 credit per operation, and an operation is “a single module run to process data or check for new data.” The counting rules from Make’s help page on how features use credits:

Module or feature	Credits
Trigger	1 per run, “regardless of whether they return data”
Search	1 per run, even when it returns many rows
Action	1 per bundle it processes (10 rows in, 10 credits)
Aggregator	1 per aggregation
Iterator	1 to split the array, then 1 per bundle in each module after it
Routers, filters, error handlers (Rollback, Break, Resume, Commit, Ignore)	0
Subscenario and scenario modules, Make Functions	0
Make Code	2 per second of run time
Fixed-size actions like a Google Drive upload	1, whatever the file size

Make’s own examples show how fast bundles multiply. A Google Forms scenario whose trigger returns 10 responses, followed by three modules, uses 1 + (3 × 10) = 31 credits in one run. A Sheets-to-Gmail scenario that sends 10 separate emails uses 11; adding a Text aggregator so it sends one combined email drops that to 3.

The difference from Zapier matters for comparisons. Zapier’s help center says “Zap triggers never use tasks,” and filters, Paths and Formatter steps don’t either. On Make, the trigger costs a credit, but routers and filters are free.

Does a Make scenario cost credits when nothing happens?

Yes, if it polls. A polling trigger checks for new data on a schedule, and each check is a trigger run. Make’s default schedule is every 15 minutes. Here’s what the checks alone cost in a 30-day month, before any action runs:

Schedule	Checks a day	Credits a month (30 days)	Share of Core’s 10,000
Once a day	1	30	0.3%
Every hour	24	720	7%
Every 15 minutes (default)	96	2,880	29%
Every 5 minutes	288	8,640	86%
Every minute	1,440	43,200	432%

That’s 4 checks an hour × 24 hours × 30 days = 2,880 for the default setting. One scenario left on the default schedule uses almost three times the Free plan’s 1,000 credits: at 96 credits a day, it runs dry in about 10 days (1,000 ÷ 96 = 10.4). A scenario polling every minute needs more than four Core allowances before it does any work.

The fix is the trigger type. Make’s scheduling docs say some triggers can run “Immediately”: they wait for a webhook or instant event instead of polling, so they only run when there’s something to process. Make’s default limit for these is 100 runs a minute; runs above it are queued. If the app you’re watching offers an instant trigger, use it. If not, set the longest interval your process can live with, or a daily schedule.

What do extra credits cost on Make?

When you run out, scenarios stop. Make’s FAQ says webhooks queue up to your storage limit and polling scenarios pick up from their last successful run once you add credits. You have three options: move to a higher credit tier, buy extra credits by hand, or turn on auto-purchase.

Since November 6, 2025, Make’s help center says “All extra credits include a 25% additional cost,” bought manually or automatically. The per-credit base is your plan’s own price divided by its credits. Applied to the US entry prices (our arithmetic on Make’s formula):

Plan (10,000 credits)	Base per credit	Extra per credit (+25%)	1,000 extra	10,000 extra
Core, billed yearly ($12)	$0.0012	$0.0015	$1.50	$15.00
Core, billed monthly ($16)	$0.0016	$0.0020	$2.00	$20.00
Pro, billed yearly ($21)	$0.0021	$0.002625	$2.63	$26.25
Teams, billed yearly ($38)	$0.0038	$0.00475	$4.75	$47.50

The rules around them:

• Units. Manual purchases come in multiples of 1,000 credits; auto-purchase buys 10,000 at a time.
• Auto-purchase cap. Auto-purchasing stops once it has bought as many credits as your plan includes. Make’s example: an 80,000-credit plan can auto-purchase at most 8 times a cycle. On a 10,000-credit plan that’s one auto-purchase. Make’s FAQ lists auto-purchase for Core, Pro and Teams.
• Card only. Both methods need a credit or debit card; if the payment fails, scenarios pause.
• Data transfer can trigger it too. Make says running out of data transfer can set off an auto-purchase while you still have credits.
• Expiry. On monthly plans, extra credits expire at the end of the billing cycle. On annual Pro and Teams plans they last until the end of the billing year. On annual Core, they expire at each monthly reset, along with your plan credits.

Make also says higher tiers cost less per credit, so if you buy extras every month, a bigger tier is usually cheaper. Make’s help center gives two examples (prices as Make printed them; it doesn’t say which country or billing cycle): Core at $113.85 for 150,000 credits, or $0.000759 a credit, and $338.13 a month for 500,000 credits, or about $0.000676 a credit. Compare that with $0.0012 at the US 10,000-credit Core tier. Make doesn’t publish the full tier table outside its slider, so check it there before you commit.

Core vs Pro vs Teams: what changes besides the price?

All three start with 10,000 credits, so the difference isn’t the allowance. From Make’s help pages and pricing page:

• How annual credits arrive. On an annual Pro or Teams plan, “all credits for your plan and tier are allocated at once”: you get a year’s worth, for example 120,000, to use when you like. Core “always” gets monthly credits, even on an annual plan. If your volume is seasonal, such as a busy sales quarter, annual Pro absorbs the peaks; annual Core resets every month and any unused credits are gone.
• Ceilings. Since November 2025, Core tops out at 300,000 credits a month; Pro goes up to 8 million.
• Teams. The Teams plan adds teams and team roles.
• Your own AI key. Since November 6, 2025, every paid plan, Core included, can connect its own OpenAI or Anthropic account for Make AI Agents and the AI Toolkit. The Free plan can’t.

Every plan also gets a usage allowance that grows with credits. Per 10,000 credits a month: 5 GB of data transfer, 10 MB of data storage, 10 MB of storage for incomplete executions (2 GB maximum) and a webhook queue of 667 (10,000 maximum). The Free plan has 1 MB of data storage and one data store.

What does AI cost on Make?

AI steps are where credit use stops being predictable. With a custom connection to your own OpenAI or Anthropic account, Make charges 1 credit per operation and you pay the provider for tokens. With Make’s AI Provider, you pay Make in credits for the tokens too. Make publishes how many tokens one credit buys:

Make AI Provider model	Input tokens per credit	Output tokens per credit
Small and Medium (GPT-5 nano)	18,080	2,260
Large (GPT-5 mini)	3,616	452
Claude Haiku 4.5	904	181
Claude Opus 4.7	180	36

Worked example (illustrative token counts): an AI step that reads a 2,000-token email and writes a 300-token summary.

• On the Large tier: 2,000 ÷ 3,616 = 0.55 credits plus 300 ÷ 452 = 0.66, about 1.2 credits for tokens, plus 1 for the operation.
• On Claude Opus 4.7: 2,000 ÷ 180 = 11.1 plus 300 ÷ 36 = 8.3, about 19.4 credits for tokens, plus 1 for the operation.

At 1,000 emails a month, that’s roughly 2,200 credits against roughly 20,400: the second doesn’t fit in Core’s 10,000. Make doesn’t say how it rounds fractional credits. For AI agents compared across builders, see our no-code AI agent builders guide.

What does the same workflow cost on Make, Zapier and n8n?

The workflow: a new lead arrives, and four actions run (add to CRM, add to a sheet, send a Slack message, send an email). On Make that’s 5 credits a run with an instant trigger; on Zapier it’s 4 tasks, since triggers are free; on n8n Cloud it’s 1 execution, since n8n counts a whole workflow run. Prices billed yearly: Make from our data (October 18, 2026), Zapier from its pricing page (read November 9, 2026, matching our data at its lowest tiers), n8n Cloud from our data (October 17, 2026, euros only).

2,000 leads a month

• Make: 2,000 × 5 = 10,000 credits. Core, $12 a month: $144 a year.
• Zapier: 2,000 × 4 = 8,000 tasks, which needs the 10,000-task Professional tier at $129 a month: $1,548 a year.
• n8n Cloud: 2,000 executions fits Starter’s 2,500, at €20 a month: €240 a year.

The same 2,000 leads with a polling trigger every 15 minutes

On Make: 2,880 checks + (4 × 2,000) actions = 10,880 credits, 880 over Core. Buying 1,000 extra each month at $1.50 brings Core to $13.50 a month, or $162 a year. On annual Core the extras expire at each monthly reset, so you buy them every month. Zapier and n8n don’t charge for polling checks that find nothing.

10,000 leads a month

• Make: 10,000 × 5 = 50,000 credits. Our data has no US price for the 50,000-credit tier. As a ceiling: Core at $12 plus 40,000 extra credits at $1.50 per 1,000 = $12 + $60 = $72 a month, if Make lets you buy that many by hand (it doesn’t publish a manual limit). A 50,000-credit tier will cost less, because Make prices bigger tiers lower per credit.
• Zapier: 40,000 tasks needs the 50,000-task Professional tier, $289 a month: $3,468 a year.
• n8n Cloud: 10,000 executions is exactly Pro’s allowance, €50 a month: €600 a year.

Monthly volume	Make (US, yearly)	Zapier Professional (yearly)	n8n Cloud (yearly)
2,000 runs, instant trigger	$12/mo	$129/mo	€20/mo
2,000 runs, 15-minute polling	$13.50/mo	$129/mo	€20/mo
10,000 runs	Up to $72/mo (less on a bigger tier)	$289/mo	€50/mo

The order changes with the shape of the workflow. A short workflow with many small runs, or one with an iterator over many items, uses more Make credits per run; n8n’s per-run count isn’t affected by the number of steps. Our Zapier pricing guide and n8n pricing guide cover those tiers in full, and Make vs Zapier sets the two side by side.

What to watch for

• Your country sets the price. US visitors see higher prices than UK, German or Canadian visitors. Check the price you’re shown at checkout, not a figure from a review.
• Idle polling burns credits. Each trigger check is a credit, even with no new data. Use instant triggers where you can.
• Iterators multiply. Every module after an iterator costs a credit per item. Make’s attachment example uses 6 credits to split and upload 5 files.
• Unused credits expire. Make’s FAQ says unused plan credits expire at the end of the term, and Core’s reset every month even on an annual plan. When you cancel, Make says “We don’t transfer your unused credits to that Free plan.”
• Extras cost 25% more. If you buy extra credits most months, price the next tier up instead.
• No cash refunds. Make “has a no cash refund policy.” When you upgrade, unused credits become a discount on the new bill; when you downgrade, they move to the new plan for 30 days (monthly) or 365 days (annual). Either change bills you straight away and starts a new billing cycle.
• Downgrades can stop scenarios. The FAQ says scenarios that use higher-plan features are stopped when you downgrade.
• Cancelling. Only the Owner or an Admin can cancel. Your paid plan runs to the end of the cycle or term, then the organization moves to Free, unless you already own a Free organization, in which case the extra organization becomes unlicensed and can’t run scenarios.
• Pausing is monthly only. Owners and Admins can pause a monthly self-service plan; annual, Free and Enterprise plans can’t be paused.
• Zapier changes on December 1, 2026. Zapier’s help center says that from that date, “Next Gen Zaps” count at least 1 task per run even if a run uses only filters or formatting. Recheck Zapier comparisons after that date.

Which Make plan should you choose?

• Testing or one daily task: Free. 1,000 credits covers a daily scenario of up to about 33 credits a run (1,000 ÷ 30 days), but not a scenario polling every 15 minutes.
• A solo user or small business with a few workflows: Core at $12 a month billed yearly. Pay monthly ($16) for the first month or two while you learn your real credit use, then switch.
• Seasonal volume, or you want credits that last the year: annual Pro at $21 a month. The year’s credits arrive at once, and extra credits last until the year ends.
• Several people building scenarios together: Teams at $38 a month billed yearly, for teams and team roles.
• Long workflows at high volume, and you can run a server: price n8n, which counts a whole run as one execution, or self-host n8n.
• You need a specific app Make doesn’t have: compare against Zapier, then see the other options on our automation hub and in Zapier alternatives.

Sources

• Make: Pricing (US), text, allowances and FAQ read November 9, 2026 (prices load with JavaScript; plan prices from AskGPU’s data, checked October 18, 2026)
• Make Help: Credits, read November 9, 2026
• Make Help: How features use credits, read November 9, 2026
• Make Help: Operations, read November 9, 2026
• Make Help: Extra credits, read November 9, 2026
• Make Help: Adjustments to plans and pricing, read November 9, 2026
• Make Help: Monthly and annual subscriptions, read November 9, 2026
• Make Help: Change your subscription, read November 9, 2026
• Make Help: Cancel your subscription, read November 9, 2026
• Make Help: Pause your subscription, read November 9, 2026
• Make Help: Schedule a scenario, read November 9, 2026
• Zapier: Plans and pricing, read November 9, 2026
• Zapier Help: How is task usage measured in Zapier?, read November 9, 2026
• Make US plan prices and country notes, n8n Cloud prices: AskGPU price data (Make checked October 18, 2026; n8n Cloud October 17, 2026)