Make.com Pricing 2026: Everything You Need to Know

Q: Can I try Make for free

Yes. The free plan gives 1,000 operations/month and 2 active scenarios — enough to build and test real workflows before committing.

Q: What happens when I run out of operations

Your scenarios pause until the next billing cycle. You won't be charged extra unless you've enabled auto-purchase of additional operations. No surprise bills.

Q: Is the annual plan worth it

If you've used Make for a month and it fits your needs, yes. The ~20% savings are meaningful over a year. But start monthly to test.

Q: Can I downgrade plans

Yes, you can downgrade anytime. Active scenarios that exceed the lower plan's limits will be paused until you adjust.

Q: How does Make handle errors

Make has the best error handling in the automation space. You can define error routes with retry, ignore, commit, or rollback behaviors — all visually. Error handler executions only count as operations when they actually trigger. --- *Last updated: March 2026. Check make.com/pricing for current rates.*

Make (formerly Integromat) has become the go-to automation platform for teams that outgrow Zapier's pricing. But Make's pricing model — based on "operations" — confuses newcomers. Here's the complete breakdown.

Make.com Plans (March 2026)

Plan	Monthly Price	Operations/Mo	Scenarios	Key Features
Free	$0	1,000	2 active	Basic modules, 5-min intervals
Core	$9/mo	10,000	Unlimited	1-min intervals, all modules
Pro	$16/mo	10,000	Unlimited	Priority execution, custom variables
Teams	$29/mo	10,000	Unlimited	Team management, roles, shared scenarios
Enterprise	Custom	Custom	Unlimited	SSO, audit logs, dedicated support

Annual billing saves ~20%. Extra operations available: 10,000 for ~$9/mo on Core.

Understanding Operations

This is the most important concept in Make's pricing — and where most people get confused.

An operation = one action performed by one module in a scenario.

Example scenario: "When a new form submission arrives (1 op) → Create a CRM contact (1 op) → Send a welcome email (1 op) → Post to Slack (1 op)"

That's 4 operations per run. If the form gets 100 submissions/month: 4 × 100 = 400 operations.

What Counts as an Operation

✅ Each module that processes data (triggers, actions, searches)
✅ Each item processed in a loop (10 items through a module = 10 operations)
✅ Iterator/aggregator modules count per item
❌ Routers (branching) are free
❌ Error handlers don't count unless triggered
❌ Filters don't count (but filtered-out items still count for the trigger)

The Batch Processing Gotcha

If your trigger pulls 50 new items at once and processes each through 3 modules, that's 50 × 3 = 150 operations per run. This catches people off guard with high-volume triggers.

Use filters early in your scenario to skip irrelevant items before they consume operations on subsequent modules.

How Much Will You Actually Spend?

Light Usage (Solo founder, <10 automations)

5-10 simple scenarios, ~500 runs/month
Operation estimate: 1,500-3,000/month
Plan: Free or Core ($9/mo)
Annual cost: $0-108

Medium Usage (Small team, 10-30 automations)

15-30 scenarios with moderate complexity
Operation estimate: 8,000-25,000/month
Plan: Core ($9/mo) + extra operations, or Pro ($16/mo)
Annual cost: $108-250

Heavy Usage (Agency/business, 30+ automations)

30+ scenarios, high-volume triggers, complex logic
Operation estimate: 50,000-200,000/month
Plan: Teams ($29/mo) + extra operation packs
Annual cost: $350-1,000+

Make vs Zapier: The Pricing Reality

This is why most people switch from Zapier to Make. Same scenario comparison:

Scenario: 20 workflows, average 4 steps, 50 runs each per month

Platform	Calculation	Cost
Zapier	20 × 4 × 50 = 4,000 tasks	$49/mo (Professional)
Make	20 × 4 × 50 = 4,000 ops	$9/mo (Core)

Make is 5x cheaper for the same workload. The gap widens with more complex scenarios because Make's Core plan includes 10,000 operations vs Zapier Professional's 2,000 tasks.

Tips to Optimize Your Make Costs

1. Use Filters Aggressively

Place filters as early as possible in your scenario. Every module a filtered item skips saves an operation.

2. Batch with Aggregators

Instead of sending 50 individual Slack messages, aggregate into one digest message. 50 operations → 1 operation.

3. Use Webhooks Instead of Polling

Webhook triggers only fire when events happen. Polling triggers run on schedule whether or not there's new data (though only matching items count as operations).

4. Consolidate Scenarios

Two 3-module scenarios = 6 ops per event. One 5-module scenario (with shared logic) = 5 ops per event. Small savings that compound.

5. Monitor Usage

Make's dashboard shows operation consumption per scenario. Check monthly and identify scenarios burning disproportionate operations.

Is Make Worth It?

Yes, if:

You run multi-step automations (Make's pricing advantage grows with complexity)
You're switching from Zapier to save money (most users save 50-80%)
You like visual workflow building (Make's canvas is the best in the industry)
You need error handling and conditional logic without code

Maybe not, if:

You need an app integration only Zapier supports (check first)
Your team is entirely non-technical (Make has a slightly steeper learning curve)
You have very simple, single-step automations (the free tier of either works)

Skip Make, if:

You're technical and want free → self-host n8n
You need maximum app coverage → Zapier
You want the absolute cheapest cloud option → Activepieces ($5/mo)

FAQ

Can I try Make for free?