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
Which Make plan fits your workflow?
Before choosing a plan, identify the exact steps and the result you need. An allowance alone does not tell you the cost of your workflow.
START WITH THE STORY
Still copying an incoming response into a sheet—and unsure another subscription will help?
Fictional scene: one possible hesitation before a small test. Skip to the plan checklist.
The scene is illustrative. For the real Make Custom Webhook → Google Sheets route, inspect both the destination row and the credit counter. Our separate recorded result follows.
What three small handoffs consumed in our test
On September 9, 2026, our Custom Webhook to Google Sheets Add a Row test completed three synthetic handoffs. Each wrote one source value. The Free account credit readings were 996, 994, 992 and 990: a decrease of two per run, six in total. Requests were queued and processed manually. This is one measured route, not a price quote, a monthly capacity guarantee or a comparison with Zapier billing. Recovery and duplicate handling remain untested.
Define one small route first. Check its actual usage and destination result before estimating a month; retries, different modules and other account activity may change consumption.
Last verified: 2026-09-30 JST. Prices and plan limits can change; confirm the official pricing page before purchase.
Decision guidance updated: 2026-10-12 JST.
BEFORE YOU CHOOSE A TIER
Check need, usage, then fit.
- Need: if the native connection or your current AI agent completes the job with acceptable oversight, keep it. Check the smallest suitable setup.
- Usage: use the Make.com Credits Calculator for fixed-credit monthly planning. Its measured 2-credit example covers one small route, not every module or AI usage.
- Fit: check the feature and timing limits below. If you are comparing products, review Pabbly Connect and Make against your actual handoff.
Stay on the smallest suitable plan while you validate the route. Upgrade only when a specific limit prevents the job you need.
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 10k-credit tier; check the official price for your selected billing cycle. | Ongoing automations needing more control and capacity. |
| Pro | OFFICIAL FACT 10k-credit tier; check the official price for your selected billing cycle. | Advanced users needing priority execution, custom variables, and full-text execution-log search. |
| Teams | OFFICIAL FACT 10k-credit tier; check the official price for your selected billing cycle. | 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 branching and iteration can cause downstream actions to run more often, while searches, retries, AI features and additional modules may change consumption.
What Oravenda actually tested on Free
TESTED BY ORAVENDA Our September 9 test used three separate synthetic inputs and wrote one source value per input, within the existing Free allowance. The six-credit decrease is a usage observation, not a paid invoice. Earlier single-run demonstrations are separate evidence; none establishes long-term capacity or reliability.
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.