Make.com's free plan: is it enough?
This page contains paid links. We get commissions for purchases made through them, at no extra cost to you.
Short answer
The free plan gives you 1,000 credits a month, 2 active scenarios and a 15-minute minimum interval on scheduled runs. For one or two simple automations it is genuinely enough. The limit that stops most people is not the credits — it is two scenarios. If you need a third, the $9 Core plan removes that cap entirely.
How credits are actually spent
Make charges per module execution, not per scenario run. Every module that fires costs one credit. That means the shape of your scenario decides your monthly bill far more than how often it runs.
| Scenario shape | Credits per run | Runs on 1,000 credits |
|---|---|---|
| Trigger → one action | 2 | ~500 |
| Trigger → filter → action | 3 | ~333 |
| Trigger → router → 2 actions → notify | 5 | ~200 |
Three ways to make the free plan last longer
- Filter as early as possible. A filter placed right after the trigger stops irrelevant runs before they spend credits downstream. A filter at the end wastes everything before it.
- Merge scenarios instead of adding them. With only two slots, one scenario with a router beats two separate ones — and often costs fewer credits than running both.
- Fix failing scenarios immediately. A run that dies halfway has already paid for the modules it reached. A broken scenario firing hourly can drain a month's credits in days.
Plans and prices
| Plan | From | What changes |
|---|---|---|
| Free | $0 | 1,000 credits, 2 scenarios, 15-min interval |
| Core | $9/mo | Unlimited scenarios, 1-minute interval |
| Pro | $16/mo | Priority execution, custom variables, log search |
| Teams | $29/mo | Team roles, shared templates |
Plan limits and prices as listed on Make's pricing page in August 2026. Make adjusts credit allowances periodically — check the current page before choosing a tier.
Common questions
How many automations can 1,000 credits actually run?
Divide 1,000 by the number of modules in your scenario. A two-module scenario — trigger plus one action — costs about two credits per run, so roughly 500 runs a month. A five-module scenario with a router and a filter costs five, which is 200 runs. The module count matters far more than the number of scenarios.
Which limit do people hit first — credits or scenarios?
Scenarios, almost always. Two active scenarios sounds fine until you want one for sign-ups, one for payments and one for a weekly report. Credits tend to last longer than beginners expect because early volume is low.
Does the 15-minute interval mean my automation is always delayed?
No. That interval applies to scheduled scenarios that poll a source. A scenario triggered by a webhook fires as soon as the request arrives, on the free plan too. If instant matters, build around webhooks rather than polling.
Do failed runs consume credits?
Modules that executed before the failure do. A scenario that dies on module four has already spent three credits. Scenarios that fail repeatedly are the most common reason a free account runs dry earlier than the maths suggested.
Is Core at $9 worth it over free?
If the scenario limit is what is blocking you, yes — Core removes it entirely and drops the scheduling interval to one minute. If credits are what is blocking you, look at your module count first: trimming a five-module scenario to three cuts consumption by 40% and costs nothing.
Related
Prices change. We recheck them by hand.
Every price on this site comes from the tool’s own pricing page, with the date we read it. When one changes — or a tool loses the program that pays us — you get one short email. Nothing else.