Make.com Pricing 2026: Plans, Credits, and Cost Guide
Make.com pricing is operation-based: each module execution counts as one credit. Most teams overspend because they estimate by workflow count, not by execution volume. This guide breaks down 2026 plans, how credits work, and how to predict your real monthly cost.
Plan structure (verified March 2026)
Verified against Make's official pricing page:
| Plan | Monthly price | Credits | Key limits |
|---|---|---|---|
| Free | $0 | 1,000/mo | 15-min min interval, 2 active scenarios |
| Core | $9 | 10,000 | 1-min interval, unlimited scenarios, Make API |
| Pro | $16 | 10,000 | Priority execution, custom variables, full-text log search |
| Teams | $29 | 10,000 | Team roles, scenario templates |
| Enterprise | Custom | Custom | Overage protection, SSO, 24/7 support |
All paid plans start at 10,000 credits. Higher credit tiers (20k, 40k, 80k...) scale proportionally. Annual billing saves ~15%.
What counts as one credit?
Each module action = one credit. Examples:
- Add a row to Google Sheets
- Fetch Gmail account data
- Send a Slack message
- One API call via HTTP module
- One loop iteration — an iterator with 50 items runs the next module 50 times = 50 credits
Make Code (JavaScript/Python) uses 2 credits per second of execution time. Data transfer: 5 GB per 10,000 credits.
Cost estimation formula
monthly credits ≈ records × module steps per record × runs per month
Example: Lead enrichment workflow, 5,000 leads/month, 6 modules per lead:
- 5,000 × 6 = 30,000 credits → exceeds base 10k allocation; plan for Core + add-on or higher tier
How to reduce Make costs
| Tactic | Why it helps |
|---|---|
| Filter early | Reject low-value records before enrichment or AI steps |
| Reduce module depth | Merge or remove low-value steps |
| Batch writes | Bulk Add Rows vs one Add Row per record |
| Separate hot vs cold paths | Run expensive modules only for high-priority records |
| Monitor retries | Failed runs and retries consume credits silently |
Free plan: what fits
The free tier works for:
- Form submission alerts to Slack
- Basic Google Sheets sync (low volume)
- Daily digest automations
- Lightweight lead capture (minimal enrichment)
It usually fails for:
- High-volume ecommerce monitoring
- Heavy AI scoring on every record
- Tight scheduling (15-min minimum)
- Many parallel active scenarios (limit: 2)
Overage and add-ons
When you exceed your credit allocation:
- Free: Scenarios stop until next month
- Paid: Add-on credit packs available; Enterprise includes overage protection
Always monitor usage in the first weeks of a new scenario.
Make vs Zapier pricing mindset
| Factor | Make | Zapier |
|---|---|---|
| Unit | Operation (credit) | Task |
| Free tier | 1,000 credits | 100 tasks |
| Entry paid | $9/mo (10k) | ~$20/mo (750 tasks) |
| Complex workflow | Only executed branches consume credits | Every step and branch = task |
Benchmark one real workflow on both platforms over a week before committing. For branching flows, Make often costs 3–4x less.
Which plan fits which team?
| Team type | Recommended plan |
|---|---|
| Learning, personal use | Free |
| Solo operator, moderate volume | Core or Pro |
| Small team, shared scenarios | Pro or Teams |
| Agency, multi-client | Teams |
| Enterprise, governance-heavy | Enterprise |
Validate against your real run profile, not generic averages.
Run a pricing test first
Before selecting a paid tier:
- Build one production-like scenario
- Run with controlled sample data (e.g., 100 records)
- Check operations consumed in execution history
- Extrapolate to monthly volume
Build one scenario from your top use case and measure one week of real usage before committing to annual billing. Open Make →
Yes. Make offers a free tier with 1,000 credits/month, 15-minute minimum scheduling, and 2 active scenarios. See free plan limits for details.
Each module action in your scenario counts as one credit: reading/writing data, API calls, sending messages, or one loop iteration. More steps and more records increase consumption.
Filter records early, reduce unnecessary modules, batch writes where possible, and run expensive steps only for high-value records. Retries also consume credits—monitor failed runs.
Yes. Annual billing saves approximately 15% compared to monthly. Credits for annual plans expire after 12 months instead of each month (Teams/Enterprise).