[Verified] How fast does Make's free 1,000 credits actually run out? It depends on workflow complexity.

Make’s credit system: every step costs one point

Make, a visual workflow automation platform, lets you chain over 2,000 apps together—from Slack to Google Sheets to custom APIs. Until recently it counted costs in “operations”; since 2026 it rebranded that to “credits.” The shift matters because of how Make bills: each module (each step in your workflow) costs 1 credit when it runs, not just the main actions.

That means a ten-step workflow burns ten credits per run, a twenty-step one burns twenty. Add filters and routers—they cost credits too. This is different from competitors like Zapier, which doesn’t charge for the trigger step, or n8n, which doesn’t meter by step count at all if you self-host.

Free users get 1,000 credits per month. Whether that’s “enough” hinges entirely on what you’re automating.

The hidden cost: every filter, every branch

Make includes a free tier that doesn’t require a credit card to start. You get 1,000 credits per month, up to 2 active workflows (called scenarios), a 15-minute minimum scheduling interval, a 5-minute runtime limit per execution, and 5 MB maximum file size. Unused credits don’t roll over to the next month.

The gotcha: both the official pricing page and most third-party guides gloss over how fast those credits vanish on complex workflows. A two-step automation (trigger + one action) uses 1 credit per run. But a seven-step flow (trigger + five transformations + one write) uses 5 credits per run. If you run that daily, that’s 150 credits per month just on one workflow.

More than half your free budget gone on a single automation.

Add a second active scenario (which you’re allowed) and the math gets tighter quickly. A typical user combining a few real-world workflows (say, one that syncs Slack messages to a spreadsheet, another that creates support tickets from email, a third that backs up cloud files) easily exhausts the 1,000-credit allowance in four to six weeks.

When does upgrading actually make sense?

Make’s paid tiers start at US$9 per month (US$16 Pro, US$29 Teams, Enterprise custom). Even at the entry level you get the same 10,000 credits per month as all paid tiers below Enterprise—the difference is features, not quota.

Core (US$9/month annual) adds unlimited scenarios, a 1-minute scheduling minimum (vs. 15 minutes free), Make API access, 40-minute execution limits, and 100 MB file uploads. No logs beyond 30 days, no custom variables, no priority queuing. Pro (US$16/month) layers in searchable execution logs, custom variables, and priority execution during peak times. Teams (US$29/month) adds multi-user access, role-based permissions, and template sharing.

The credit budget is identical across all three: 10,000 per month, enough for a hundred 10-step workflows running daily, or smaller teams with dozens of automations.

Enterprise pricing is custom and requires a conversation with sales—you get SSO, 60-day log retention, 24/7 support, and compliance features like custom integrations.

🔍 AMPM exclusive check

We verified Make’s pricing page directly on 2026-09-08 and again before publication. The numbers in this article—1,000 free credits per month, 2 active scenarios, 15-minute scheduling, 5-minute execution limit, 5 MB files—match the official Make.com pricing page exactly. The US$9, US$16, US$29 annual pricing is accurate; monthly rates run about 15% higher (roughly US$10.59 for Core, US$18.82 for Pro, US$34.12 for Teams).

What Make’s pricing page does not emphasize: the per-step credit cost. The page lists that “each operation consumes 1 credit” but buries the detail that filters and routers are operations too. It doesn’t include a worked example of a realistic three- or five-step workflow to show how fast credits actually deplete. You have to build a test scenario or email support to understand the real-world impact. That gap is why credit consumption feels surprising to new users.

Nothing else differed from the official claims this time; verified 2026-09-08.

☀️ AMO, the budget-minded cat

If you’re a solo user or small team on a tight budget, Make’s free tier starts strong: unlimited app integrations (350+ include AI tools, plus MCP server support), the Maia AI assistant (write workflows in natural language), and access to beta Make AI Agents for free. No credit card needed to register. You can build real automations and keep them running month after month without spending a cent.

But “free” only works if your workflows are simple. A one-step trigger-to-action automation—say, send me a Slack message when someone fills a form—uses 1 credit per trigger. Run it 50 times a day and you’ve burned 1,500 credits in a month. You hit the wall fast.

The smarter budget approach: keep the free tier for lightweight, low-frequency tasks (weekly reports, monthly backups, one-off notifications). For anything that runs daily or involves multiple steps, US$9 per month for Core is worth it. That gets you 10,000 credits, unlimited scenarios, and 1-minute scheduling intervals instead of 15. At that rate you can run even moderately complex workflows (five to ten steps, a few times daily) without sweating your quota.

For a lean startup or bootstrapped business, Core at US$9 annually amortizes to less than a cent per daily automation. The jump to Pro (US$16) is only worth it if you’re debugging failed runs constantly or managing dozens of concurrent workflows. Teams (US$29) is for actual multi-person teams—single operators rarely need it.

Verdict for AMO: free tier is real, but plan to upgrade within a month or two if you’re actually automating work. Then US$9/month Core is genuinely cheap.

🌙 PIMI, the performance-minded cat

If you’re running production automations—handling customer data, syncing business systems, or managing critical workflows—the free tier’s constraints are showstoppers. Two active scenarios isn’t enough for most operations. A 15-minute scheduling minimum means you can’t react to events in real time. Five-minute execution limits strangled any workflow touching an API that doesn’t respond in milliseconds. And 5 MB file limits break anything involving documents or bulk data.

Pay for Core (US$9/month) and you fix most of that: unlimited scenarios, 1-minute scheduling, 40-minute execution, 100 MB files. Ten times the file size, 15 times faster trigger response, and enough runtime for most integrations to complete without timeouts.

Pro (US$16/month) is where performance users start seeing real value. Priority execution means your workflows jump the queue during peak hours—important if Make is handling time-sensitive tasks. Searchable logs let you actually debug failures instead of scrolling through 30 days of opacity. Custom variables make it easier to manage configuration across workflows.

At 10,000 credits per month across Core, Pro, and Teams, the bottleneck is rarely quota for production use; it’s usually feature access. A moderately complex integration (Slack → Salesforce → email notification) might use 8-12 credits per run. Run it 100 times a day and you’re at 24,000-28,800 credits per month—you’d hit the 10,000 limit and need to contact sales for higher tiers.

That’s the ceiling where Make becomes a conversation about scale and spend, not a self-serve SaaS purchase.

Verdict for PIMI: Core works for small-to-medium workflows. Pro adds visibility. Teams adds governance. Pick based on how many people touch your automations and how mission-critical they are. Budget conservatively on credit consumption; real workflows cost more than the spreadsheet.

Verdict: who should use it, who should skip it

Use Make if you want visual, no-code workflow building with massive app coverage and are willing to pay US$9–US$29 per month for reliability. The free tier is real enough for prototyping but too tight for regular use. Core’s price is hard to beat.

Skip it if you need unlimited workflows on a hard budget—self-hosted n8n (no per-step billing) or Zapier’s free tier (no per-step charge for triggers) might be better. Also skip if you need sub-minute scheduling or complex workflows with hundreds of steps, since credit costs add up fast.

Watch out for the credit consumption cliff: simple workflows feel cheap, but each step stacks. Build a prototype first, count the credits it burns, and then decide if monthly spend makes sense for your use case.

Written: 2026-09-23

Price last verified: 2026-09-08

Tool last health-checked: 2026-09-23

🔗 Related on AMPM

• Make pricing & free tier

📎 Sources

All prices and quotas in this article come from AMPM’s verified dataset for Make (last verified 2026-09-08); primary sources:

• https://www.make.com/en/pricing
• https://www.make.com

🐾 Meet the cats: AMO and PIMI

AMPM is a Taiwan-based AI-tool pricing watchdog. Our motto: ask before you subscribe. Two cats argue every tool from two sides:

• ☀️ AMO — the budget-minded cat. Always asks: is the free tier enough, and is paying actually worth it?
• 🌙 PIMI — the performance-minded cat. Cares about whether it works well, fast, and gets your job done.

When they are done arguing, you know whether to pay. Every number is checked by us, with the verification date at the end.

🐾 Our sister sites also checked

• Brokerage fees and account opening checked