Make.com pricing explained: what it really costs in 2026

Make is the right call for teams running multi-step automations at real volume. Skip it if you have fewer than five scenarios to automate, need the widest possible app catalog on day one without configuration, or want non-technical teammates building Zaps without any training. For teams that have hit Zapier's task ceiling or need loops and conditional logic, Make's credit pricing is cheaper. Budget 30 minutes to understand how credits work before picking a plan.

Plan tiers

Plan	Monthly (annual)	Credits/month	Active scenarios
Free	$0	1,000	2
Core	$9	10,000	Unlimited
Pro	$16	10,000	Unlimited
Teams	$29	10,000	Unlimited
Enterprise	Custom	Custom	Unlimited

All three paid tiers start at 10,000 credits. The price difference buys features, not more credits. Pro adds priority execution and full-text log search. Teams adds shared roles and templates. Annual billing saves roughly 15%. Pricing checked June 2026 from make.com/en/pricing.

How credits actually work

One credit, one module action. A three-module scenario that runs once uses three credits. Simple.

The number that catches teams off guard: iterators. A loop that processes 500 rows consumes 500 credits for the iterator alone, before any action inside the loop fires. A scenario that pulls 500 contacts, enriches each one, and pushes each to a CRM can burn 1,500 or more credits per single run.

Two other places credits move faster than expected:

• Make Code: charges 2 credits per second of execution time, not per run
• Native AI modules: billed by token usage, so longer model responses cost more per execution and the total is hard to predict

Error handlers and the Router module are free.

Real bill math

A typical small marketing team running four scenarios:

Scenario	Modules	Frequency	Monthly credits
Form → CRM push	3	50×/day	4,500
Weekly analytics pull	6	4×/month	24
Contact enrichment loop	3 per row, 400 rows	1×/month	1,200
SMS follow-up trigger	2	40×/day	2,400
Total			~8,124

That fits inside the Core plan's 10,000 credits at $9 per month. Add one heavier enrichment run, a daily report loop, or a native AI module and you need add-on credits. Add-on packs carry a 25% cost premium over base plan rates per credit.

The part that breaks

Iterator miscounting burns most new Make users. People build a scenario, count one run as "one execution," and forget the loop multiplier. A scenario that iterates through a 2,000-row Google Sheet and fires two actions per row uses at least 6,000 credits on a single run. That is 60% of the Core plan's monthly budget, gone in one execution.

The free tier stops all scenarios the moment credits run out, with no warning. A lead follow-up or daily report simply halts mid-month until the next billing cycle.

Copy this

Estimate monthly credits before building a scenario:

monthly credits =
  (modules × runs per day × 30)
  + (iterator rows × actions inside loop × loop runs per month)
  + (Make Code runs × avg execution seconds × 2)
  + AI module overhead (estimate high; token costs vary)

example:
  4-module workflow, 20 runs/day = 2,400 base credits
  + 300-row iterator, 2 actions each, 5 runs/month = 3,000
  = 5,400 credits/month → fits Core plan with headroom

Run this before you build. If the total exceeds 8,000, start on Core with an add-on pack rather than jumping to Pro.

Upgrade path

Once the Core build is stable, layer in:

• HTTP modules instead of native AI modules: route requests through your own API keys. The HTTP call costs one credit flat regardless of token count.
• Webhook triggers instead of polling: a scenario polling every five minutes fires 8,640 times a month. Webhook-triggered scenarios fire only when data actually arrives.
• Teams plan: worth it once more than two people share scenarios. Role-based access prevents the accidental break.

See how Zapier's task billing compares or jump straight into the lead-to-CRM build to put Make credits to work. More automation builds at /topics/automation.

Frequently asked questions

How much does Make.com cost per month in 2026?+

The Free plan is $0 for 1,000 credits and 2 active scenarios. The Core plan starts at $9 per month billed annually for 10,000 credits with unlimited scenarios. Pro is $16 per month for 10,000 credits plus priority execution and full-text log search. Teams is $29 per month with shared roles. Pricing checked June 2026 from the official Make pricing page.

What is a Make credit and how many does a typical automation use?+

One credit equals one module action. A three-step scenario that runs once uses 3 credits. An iterator that loops through 500 rows uses 500 credits for the loop alone, plus one credit per action inside each iteration. Most small-team scenarios land between 1,000 and 8,000 credits per month at moderate run frequency.

When does Make.com get expensive?+

The bill climbs fast with iterator modules (each row counts as one credit), native AI modules (billed by token, not by run), and error retries (which also consume credits). Teams that estimate by workflow count rather than execution volume routinely overshoot their plan.

Is Make cheaper than Zapier at volume?+

Usually yes for multi-step or high-volume workflows. A five-step scenario running 1,000 times per month consumes 5,000 Make credits and 5,000 Zapier tasks. Make's cost per credit unit is lower than Zapier's cost per task at comparable volumes. For simple one- or two-step automations at low frequency, both cost roughly the same.