Make.com Free Plan 2026: Limits, Use Cases, and When to Upgrade
Make.com's free plan includes 1,000 credits per month, a 15-minute minimum scheduling interval, and 2 active scenarios. It is enough for learning and low-volume automations. Production-scale workflows usually require a paid plan. This guide spells out exact limits and what fits.
Free plan limits (verified March 2026)
| Limit | Free plan value |
|---|---|
| Credits | 1,000/month |
| Active scenarios | 2 |
| Minimum schedule interval | 15 minutes |
| Routers & filters | Included |
| App integrations | 3,000+ |
| Visual builder | Full access |
| Support | Customer support |
Source: Make pricing page. Always verify before launch; plans can change.
What counts toward 1,000 credits
Each module execution = one credit. Examples:
- One form submission processed through 4 modules = 4 credits
- One iterator with 20 items processing 5 modules = 100 credits
- One daily digest (1 run × 6 modules) = 6 credits/day ≈ 180/month
A typical form-to-Slack flow uses 3–5 credits per run. At 15-min intervals, 96 runs/day × 4 credits ≈ 384 credits/day—you would exhaust 1,000 in under three days. Free works when volume is low.
What you can build on free
Good free-tier projects
| Use case | Why it fits |
|---|---|
| Form to sheet + Slack alert | 3–5 modules, low volume |
| Daily KPI snapshot | 1 run/day, 5–8 modules ≈ 240 credits/month |
| Weekly digest | 1 run/week, ~10 modules ≈ 40 credits/month |
| Simple lead capture | Minimal enrichment, filter before heavy steps |
| New blog post notifier | RSS/watch trigger, 2–3 actions |
Poor free-tier projects
| Use case | Why it fails |
|---|---|
| High-volume ecommerce monitoring | Credits burn fast |
| Heavy AI scoring on every record | Each LLM call = credits |
| Frequent multi-branch scenarios | Many modules per run |
| Real-time pipelines | 15-min minimum too slow |
| 10+ active automations | Limit: 2 scenarios |
How to stay inside 1,000 credits
- Filter early — Reject records before enrichment or AI steps.
- Avoid unnecessary steps — Skip low-value modules for low-priority items.
- Run daily first — Start with 1 run/day; tighten only if needed.
- Keep one primary branch — Fewer router paths = fewer credits.
- Monitor weekly — Check execution history; adjust before hitting limit.
Four practical free-tier scenario ideas
- Form to sheet + Slack — Low volume, high value for solo operators.
- New blog post notifier — Watch RSS, send summary to team channel.
- Weekly KPI snapshot — Pull metrics from one source, write to one sheet tab.
- Simple lead triage — Collect leads, route only top-priority for review.
Signs you should upgrade
Upgrade when:
- You regularly hit 1,000 credits before month-end.
- You need faster than 15-minute scheduling.
- You need more than 2 active scenarios.
- You use team collaboration, templates, or Make API.
- Business-critical flows need priority execution or overage protection.
See pricing tiers — Core starts at $9/month for 10,000 credits.
Compliance on free
Free plan users still handle real data. Apply basic safeguards:
- Store only required personal fields.
- Set retention windows per region.
- Add region-aware routing where rules differ.
- Document data sources and consent assumptions.
Run free for two weeks first
If your workflow is in validation mode, run it on free for two weeks. Collect usage data. That gives a better upgrade decision than guesswork.
Do not upgrade after one spike. Upgrade after 2–4 weeks of consistent usage near your limit. Try Make free →
Yes. Make offers a free plan with 1,000 credits/month, 15-minute minimum scheduling, and 2 active scenarios. No credit card required.
Credits (1,000/month) and minimum scheduling (15 minutes). Each module execution counts as one credit. High-frequency or multi-module workflows exhaust the limit quickly.
Yes for low-volume capture and basic routing. High-volume enrichment and AI scoring usually need paid tiers.
Make states there is no time limit on the free plan. Limits reset monthly. Always verify current terms on the official site.