Make costs $0 on the Free plan, then $12, $21 and $38 a month billed yearly for Core, Pro and Teams. Every paid plan includes 10,000 credits a month; billed monthly, the same plans come to about $16, $28 and $51.
| Plan | Billed yearly | Billed monthly | Credits per month | Active scenarios | Fastest schedule |
|---|---|---|---|---|---|
| Free | $0 | $0 | 1,000 | 2 | Every 15 minutes |
| Core | $12/mo | about $16/mo | 10,000 | Unlimited | Every minute |
| Pro | $21/mo | about $28/mo | 10,000 | Unlimited | Every minute |
| Teams | $38/mo | about $51/mo | 10,000 | Unlimited | Every minute |
| Enterprise | Custom | Custom | Custom | Unlimited | Every minute |
That table answers most visits to this page. The rest covers the two things that decide whether Make's price actually holds for you: how credits are counted, and how many of them your scenarios burn just checking for new data.
| Products | Make Free | Make Core | NoteLinker |
|---|---|---|---|
| Price, Billed Yearly | $0 | $12/mo | $16/mo ($19 monthly) |
| Priced By | Credits (1 per module run) | Credits (1 per module run) | Flat per account |
| Included Each Month | 1,000 credits, 2 scenarios | 10,000 credits | Unlimited |
| Fastest Schedule | Every 15 minutes | Every minute | Live, no schedule |
| Notion + HubSpot | Build a scenario, copies data | Build a scenario, copies data | Live Notion rows on records |
| Best For | Testing a scenario | Multi-step automation | Notion notes on HubSpot records |
In this article
1.
2.
3.
4.
5.
6.
Which Make Plan Do You Need?
Because every paid plan carries the same 10,000 credits, you pick a plan for its features and buy credits separately.
Free, if you are testing
1,000 credits, two active scenarios, and a 15-minute minimum interval. Enough to build and prove out a scenario, not to run a scheduled one all day.
Core, for most single users
$12 a month billed yearly. Unlimited active scenarios, a one-minute minimum interval, and API access. This is the plan most people searching for Make's price end up on.
Pro, if you debug a lot
$21 a month billed yearly. Adds priority execution, custom variables, and full-text search across your execution logs. Worth it once scenarios are business critical and you need to find a failed run fast.
Teams, if several people build
$38 a month billed yearly. Adds team roles and shared scenario templates. Choose it for collaboration, not for volume.
How Make Credits Are Counted
A credit is Make's billing unit, and for standard apps the rule is simple: one module run costs one credit.
- 1
Each module that runs costs a credit
A scenario with a trigger, a search and an update costs three credits each time it processes one record. If the trigger returns five records, the modules after it run five times.
- 2
A scheduled trigger costs a credit on every check
The trigger module counts once per run whether it returns ten records or none. That is the cost most people miss, covered in the next section.
- 3
AI modules cost more
AI modules are metered by tokens, file size or execution time rather than one per run, so a single AI step can cost several credits.
Credits replaced operations on August 27, 2025, and existing balances converted one to one. For non-AI scenarios the count is the same as it was. Unused credits expire at the end of your billing term, monthly or yearly depending on how you pay.
The Cost Nobody Budgets: Scheduled Checks
This is the part of Make's pricing that surprises people, so it is worth doing the arithmetic before you choose a plan.
Most app triggers in Make are scheduled: the scenario wakes up on an interval, asks the app whether anything changed, and goes back to sleep. Every one of those wake-ups costs a credit, including the ones that find nothing. Make's own scheduling guide puts a five-minute schedule at 288 credits a day.
| How often the trigger checks | Credits per month, trigger only | Share of 10,000 |
|---|---|---|
| Every 60 minutes | 720 | 7% |
| Every 15 minutes | 2,880 | 29% |
| Every 5 minutes | 8,640 | 86% |
| Every 1 minute | 43,200 | 432% |
Two ways to bring this down. Use an instant trigger where the app supports webhooks, so the scenario only runs when something actually happens. Or slow the schedule to whatever your process can live with; hourly is often fine for reporting and back-office work.
What a Notion to HubSpot Scenario Costs on Make
Here is a common real build: when a row in a Notion client database changes, find the matching HubSpot contact by email and add the row's content as a note. Notion's "watch database items" trigger is scheduled, so the check cost applies.
Assume about 600 row changes a month:
| Schedule | Trigger checks | Search + note (600 x 2) | Total credits | Plan that covers it |
|---|---|---|---|---|
| Every 60 minutes | 720 | 1,200 | 1,920 | Core, $12/mo yearly |
| Every 15 minutes | 2,880 | 1,200 | 4,080 | Core, $12/mo yearly |
| Every 5 minutes | 8,640 | 1,200 | 9,840 | Core, with almost nothing to spare |
| Every 1 minute | 43,200 | 1,200 | 44,400 | Core plus extra credits |
So the honest answer for this build is that Make Core at $12 a month covers it comfortably, as long as a 15-minute delay is acceptable. Ask for near real time and the same scenario needs more than four times the credits in the plan.
Before you build it, check
- How fast the data really needs to arrive, because that, not the number of records, is what sets your credit use.
- Whether the trigger app offers an instant trigger, which removes the empty checks entirely.
- What happens the second time a row changes: an "add note" step adds another note, so you need extra modules to update instead of duplicate.
- Whether you want a few fields in HubSpot or the whole Notion page, because the scenario copies whatever you map, not the page itself.
If you want the Notion note on the HubSpot record, not a copy of it
NoteLinker shows your live Notion rows on HubSpot contact and deal records for a flat $19 a month. No scenario to build, no schedule, no credits.
Make Pricing vs Zapier
Per unit, Make is far cheaper. Core works out to about 0.12 cents per credit; Zapier Professional, at $19.99 a month billed yearly for 750 tasks, works out to about 2.7 cents per task, roughly 22 times more.
The catch is what each one meters. Zapier never bills a trigger check, a filter or a formatter step; it bills only successful actions. Make bills every module run, including the empty checks. So Zapier often wins for a simple flow that must react within minutes, and Make wins for multi-step or hourly flows. The full side by side, with worked numbers for both, is in Make vs Zapier.
Is Make Worth the Price?
The cheapest serious automation platform per unit, with HubSpot on every plan. Budget for the trigger checks, and use instant triggers where you can.
Costs more per unit but never bills a check. See the best Zapier alternatives if price is the sticking point.
Flat $19 a month, or $16 billed yearly. Your Notion rows appear live on HubSpot contact and deal records, with formatting intact, matched by email or deal name. Nothing to build or maintain, and a 14-day trial with no credit card.
For most automation jobs, Make is excellent value, and Core at $12 a month is hard to beat. Where it stops making sense is a job that is not really automation. A Notion note is a living document: every edit becomes a new run, a new copy on the HubSpot record, and more credits. If that is the job, showing the note in place is simpler than copying it.
If you are weighing Make against other tools, see the best Make alternatives for Notion and HubSpot and Whalesync vs Make. For other pricing breakdowns, see Activepieces pricing, Outfunnel pricing and Whalesync pricing.
Skip the credit math entirely
NoteLinker connects Notion and HubSpot in two minutes, shows your Notion notes on the records your team already opens, and costs a flat $19 a month.
Get HubSpot and Notion tips delivered straight to your inbox
We'll email you 1-3 times per week, and never share your information.