Start here when...
You are validating one or two workflows and 1,000 monthly credits gives you enough room to test.
PRICING · OFFICIAL SOURCE CHECK
Make pricing: is the Free plan enough?
A practical way to decide between Make Free, Core, Pro, and Teams without paying before you understand how credits map to your workflow.
Last verified: 2026-09-04 JST. Prices and plan limits can change; confirm the official pricing page before purchase.
30-SECOND DECISION
Upgrade when...
You need more credits, unlimited active scenarios, one-minute scheduling, higher data-transfer limits, or Make API access.
DO NOT BUY BY APP COUNT ALONE. Estimate how many module actions one real run consumes, then multiply by expected monthly runs.
Current plan snapshot
| Plan | Current listed price / allowance | Who it fits |
|---|---|---|
| Free | OFFICIAL FACT $0; up to 1,000 credits/month. | Testing, low-volume personal workflows, proof of concept. |
| Core | OFFICIAL FACT $12/month at 10k credits on the monthly selector. | Ongoing automations needing more control and capacity. |
| Pro | OFFICIAL FACT $21/month at 10k credits on the monthly selector. | Advanced users needing priority execution, custom variables, and full-text execution-log search. |
| Teams | OFFICIAL FACT $38/month at 10k credits on the monthly selector. | Shared team scenarios, templates, and role-based collaboration. |
What is a Make credit?
OFFICIAL FACT Make now uses credits as its billing unit. For common non-AI scenario actions, one module action generally consumes one credit. Reading a webhook, writing a Google Sheets row, searching data, updating data, and many built-in transformations can each consume credits.
A simple way to estimate your monthly usage
If a workflow uses 4 billable module actions per run and runs 100 times in a month, a rough first-pass estimate is about 400 credits. Real scenarios can consume more because routers, iterators, searches, retries, AI features, and additional modules change usage.
What Oravenda actually tested on Free
TESTED BY ORAVENDA Our webhook-to-Google-Sheets scenario ran at USD 0 during the controlled test. That single test does not establish long-term capacity or reliability; it only shows that this bounded workflow could be completed within the Free plan at the time of testing.
When Free is probably enough
- You are still learning the builder.
- You have a low-volume workflow.
- You can tolerate the Free plan's 15-minute minimum scheduled interval where it applies.
- You want to validate field mapping, app authorization, and destination output before paying.
When Core becomes the rational upgrade
- Your real monthly credit estimate approaches the Free allowance.
- You need unlimited active scenarios.
- You need scheduling down to the minute.
- You need Make API access or higher data-transfer limits.
Best first move: build the smallest version of the workflow on Free, measure its actual credit consumption, then upgrade only when the numbers justify it.
Affiliate link — Oravenda may earn a commission at no extra cost to you.