Make.com Pricing Explained: Operations, Tiers, and the Real Cost at Scale

How Make.com Pricing Works: You Pay Per Operation

Make's plans (Free, Core, Pro, Teams, and Enterprise) are priced primarily on operations per month, with features like advanced scheduling and permissions layering on at higher tiers. An operation is one module execution inside a scenario. Every time any module in your scenario runs (a trigger check that finds data, an action, a router branch, a filter evaluation on some plans), that's an operation. The free tier gives you roughly 1,000 operations a month, which is genuinely useful for testing and tiny workloads. Paid tiers sell operations in bundles, and the per-operation price drops as volume rises. The comparison that matters: Make's cost per operation is typically a fraction of Zapier's cost per task at equivalent volumes, often 3 to 5 times cheaper for the same real-world workload. That's the headline reason teams migrate.

The Operation-Count Surprises

Make's unit price is low, but its counting is granular. Four things inflate operation counts beyond what teams expect:

• Batch processing: a scenario that pulls 100 records and processes each one runs its downstream modules 100 times. One scheduled run can consume hundreds of operations.
• Polling triggers: scenarios that check for new data on a schedule consume an operation per check on most trigger types, even when nothing new is found
• Iterators and array handling: splitting an array into items multiplies downstream module executions by the item count
• Error retries: failed executions that retry consume operations on each attempt

When Make Is the Right Economic Choice

Make hits the sweet spot for a specific band of teams, and it's a wide band:

• You've outgrown Zapier's pricing (roughly 1,000+ runs a month) but don't want to host anything yourself
• Your workflows need real logic: routers, iterators, error handling, and data transformation that would be clumsy or expensive in Zapier
• You want a managed platform: no servers, no updates, no maintenance burden
• Your volume is moderate: thousands to low hundreds of thousands of operations a month, where Make's bundles stay affordable

When to Look Past Make: The n8n Threshold

At high volumes, even Make's cheap operations add up, and the fixed-cost model of self-hosted n8n starts winning. n8n is open source. Self-hosted, it has no per-execution charge at all: you pay for a modest server and the time to maintain it. A workload consuming hundreds of thousands of operations a month on Make might run on a $20-50/month server with n8n. The trade-offs are real: someone has to set it up, secure it, update it, and fix it when it breaks. n8n's app library is also smaller than Make's, though its HTTP module and code nodes cover most gaps. The rule of thumb we use with clients: below roughly 10,000 operations a month, the Make vs n8n cost difference rarely justifies the maintenance overhead. Well above that, or for AI-agent workflows with heavy execution counts, self-hosted n8n usually wins on pure economics. Our full n8n vs Make vs Zapier comparison goes deeper.

How to Keep Your Make Bill Down

Whatever tier you're on, scenario design drives your bill more than plan choice:

• Filter at the trigger, not mid-scenario: records rejected early never consume downstream operations
• Use webhooks instead of polling wherever the source app supports them: you stop paying for empty checks
• Batch thoughtfully: aggregate records and process them in bulk where per-item handling isn't required
• Audit scenarios quarterly: the operations report shows exactly which scenarios eat your allowance. Kill or redesign the gluttons.
• Watch retry settings: aggressive auto-retry on a flaky endpoint can quietly double a scenario's consumption