Make cost calculator

How many Make credits will your automations use in a month, and is the Free plan enough? Pick what you run, type a realistic volume, and get an estimate built from the actual blueprint files — not a guess per scenario.

An estimate, not a quote. Plans and prices as listed on Make’s pricing page, checked on .

Tick the automations you run (or plan to), then type a realistic monthly volume. The estimate updates as you type.

Start when something happens

A form, a booking or a payment fires a webhook. Make is idle until then, so these cost nothing in a quiet month.

  • 3 modules → 3 credits per event · blueprint

  • 4 modules → 4 credits per event · blueprint

  • 4 modules → 4 credits per event · blueprint

  • 3 modules → 3 credits per event · blueprint

  • 4 modules → 4 credits per event · blueprint

  • 3 modules → 3 credits per event · blueprint

  • 4 modules → 4 credits per event · blueprint

  • 3 modules → 3 credits per event · blueprint

Watch an inbox

Make checks Gmail on a schedule. Every check costs one credit, even when there is no new email.

  • 2,976 checks a month at 1 credit, plus 2 credits per email · blueprint

  • 2,976 checks a month at 1 credit, plus 3 credits per email · blueprint

Run on a schedule

Make reads a sheet at a fixed time. Each run costs a credit for the search, then more for each row it acts on.

  • Runs every day: 1 credit per run, plus 2 per row · blueprint

  • Runs once a week: 5 credits per run, whatever the volume · blueprint

  • Runs every day: 1 credit per run, plus 3 per row · blueprint

  • Runs every day: 1 credit per run, plus 2 per row · blueprint

  • Runs every day: 3 credits per run, whatever the volume · blueprint

  • Runs once a week: 1 credit per run, plus 2 per row · blueprint

  • Runs every day: 3 credits per run, whatever the volume · blueprint

  • Runs once a month: 5 credits per run, whatever the volume · blueprint

  • Runs every day: 1 credit per run, plus 2 per row · blueprint

  • Runs once a week: 5 credits per run, whatever the volume · blueprint

  • Runs every day: 3 credits per run, whatever the volume · blueprint

Ready to build it?Every blueprint listed here imports into Make. Affiliate link. If you sign up through it we earn a commission from Make; your price is the same, and the link gives you one month of Core free. Everything on this page works without the link.
Open a Make account →affiliate link

Make’s plans, as listed

Entry tier of each plan. Source: make.com/en/pricing, verified .
PlanListed priceCredits / monthActive scenariosFastest schedule
FreeFree1,0002Every 15 min
Core$12/mo10,000UnlimitedEvery 1 min
Pro$21/mo10,000UnlimitedEvery 1 min
Teams$38/mo10,000UnlimitedEvery 1 min

Paid prices are Make’s “price for 10k credits/mo”. The paid plans scale up to 8M+ credits on a slider, and annual billing is discounted; we do not quote those figures. Pro and Teams include the same credits as Core at this tier and differ in features, so volume alone never points to them.

How the estimate works

Every number comes from the blueprint file you would import. We count the modules in each scenario and read how it starts, then apply Make’s rule that each module run costs one credit:

  • Webhook automations run every module once per event: a 3-module lead alert costs 3 credits per lead.
  • Gmail-watching automations cost 1 credit per check, found or not, plus the other modules once per email.
  • Scheduled automations that act per row cost 1 credit per run for the search, plus the other modules once per row found.
  • Scheduled summaries (a search, an aggregator, one message) cost every module once per run, whatever the volume.
  • Schedules are sized for the longest month: 31 daily runs, 5 weekly runs, 1 monthly run. The plan suggestion adds 20% for test runs and retries.
  • A search that finds one match is counted once. Error handlers, re-runs you start by hand, and scenarios you build yourself are not included.
Credits per automation, read from each blueprint
AutomationModulesStarts byCredits a month
Lead comes in → logged → alert. No hands.3Webhook (instant)3 × events
Labelled email → task in the log → reminder3Watches Gmail1 × checks + 2 × emails
Invoice past due → an automatic, polite reminder3Scheduled, per row1 × daily run + 2 × rows
New client → welcome email → onboarding checklist → alert4Webhook (instant)4 × events
Weekly report → Telegram, every Sunday at eight5Scheduled, one summary5 × 5 runs = 25
Quote unanswered for 3 days → one follow-up, automatic4Scheduled, per row1 × daily run + 3 × rows
Project closed → 7 days → a Google review request3Scheduled, per row1 × daily run + 2 × rows
Returning lead → recognised → "second contact", not "new lead"4Webhook (instant)4 × events
Every morning: what is due today → one message3Scheduled, one summary3 × 31 runs = 93
Every Thursday: project status → an email to the client, without writing it3Scheduled, per row1 × weekly run + 2 × rows
Form arrives incomplete → an email asking for exactly what is missing3Webhook (instant)3 × events
A task overdue by 3 days → an alert to the consultant, not the client3Scheduled, one summary3 × 31 runs = 93
On the 1st: the month's summary → an email to the client, without opening a sheet5Scheduled, one summary5 × 1 runs = 5
"Remove me" email → marked → confirmation, within a minute4Watches Gmail1 × checks + 3 × emails
Payment received → invoice marked "paid" → a thank-you to the client4Webhook (instant)4 × events
A meeting tomorrow → a reminder 24 hours ahead, with a "can't make it" link3Scheduled, per row1 × daily run + 2 × rows
Every Sunday: leads by source → one message with the change from last week5Scheduled, one summary5 × 5 runs = 25
A lead untouched for 7 days → an alert to the salesperson, not the client3Scheduled, one summary3 × 31 runs = 93
Tally form → lead log → Telegram alert. The free version of the lead alert3Webhook (instant)3 × events
Booking form → meetings sheet → confirmation email. Feeds the no-show reminder4Webhook (instant)4 × events
Feedback score → low: instant alert; high: a review request in 7 days3Webhook (instant)3 × events

Questions

What is a Make operation?

One module doing one thing once: adding a sheet row, sending an email, searching a list. Make now bills in credits, and a standard module action costs one credit, so for the automations here one operation = one credit. A module that runs once per row runs, and costs, once per row. Make's built-in AI features can use more than one credit per action; none of our blueprints uses them.

Does the Make free plan suffice?

Often, for one business with a couple of instant automations. Free includes 1,000 credits a month and 2 active scenarios, and runs at most every 15 minutes. The scenario limit usually bites first: a third automation means a paid plan even at low volume. A Gmail-watching automation checking every 15 minutes uses about 2,976 credits a month on checks alone, more than Free includes.

Why does a quiet inbox still cost credits?

A "watch" trigger has to ask Gmail whether anything is new, and Make charges one credit per check whether or not it finds something. Checking once an hour instead of every 15 minutes cuts that cost by four; a webhook trigger avoids it entirely.

How current are the prices?

We read them off Make's pricing page on 28 September 2026 and show them with the date. Make changes plans and prices from time to time, sells larger credit tiers on a slider, and discounts annual billing. The figure on Make's own page is the one you will pay.

Want the automations themselves? All 21 blueprints are free to download, and why we build on Make.

Disclosure: this site contains affiliate links. Signing up or buying through them may earn us a commission at no extra cost to you. Recommendations come from actual use and fixed selection rules, and are not influenced by commission size. Every page also says what does not work.