Independent analysis. This page may contain affiliate links.
Make Pricing Guide: Plans, Operations, and When to Upgrade
Make, formerly Integromat, is a visual automation platform that competes with Zapier by charging for operations rather than tasks and offering more detailed, branch-heavy scenarios. Its pricing is affordable at the low end but the way it counts usage confuses newcomers.
This guide explains how operations work, what each plan includes, and how to keep costs from creeping up.
Quick comparison table
| Option | Best for | Starting price |
|---|---|---|
| Free | Testing scenarios with light usage | Free, 1,000 operations/mo |
| Core | Individuals running regular automations | From about $9/mo |
| Pro | Power users with complex scenarios | From about $16/mo |
| Teams | Departments sharing automations | From about $29/mo |
| Enterprise | Large organizations needing governance | Custom pricing |
How Make Charges: Operations Explained
Every module your scenario runs that processes data counts as an operation. A scenario that triggers, reads data, filters, and sends a message consumes several operations per run, so the monthly allowance disappears faster than the number of scenarios suggests.
Make is usually cheaper than task-based competitors for simple workflows because a run can span many steps, but complex scenarios with looping and iteration can consume operations quickly. Model your real usage before choosing a tier.
Free vs Core
The free plan gives a thousand operations and one active scenario, plus a limited interval between runs. It is enough to learn the interface and run a personal automation, but one active scenario blocks anything serious.
Core lifts the operation allowance, unlocks more scenarios, and shortens the minimum interval so runs happen more often. It is the practical starting point for a single operator automating real work.
Pro and Teams
Pro raises limits further and adds priority execution, more scenarios, and advanced features such as custom variables and full-text log search. It fits power users who run many active workflows.
Teams adds shared workspaces, roles, and collaboration features for departments. Enterprise brings governance, SSO, and higher throughput for organizations running automation at scale.
When to Move Off Make
If your usage is dominated by very simple two-step triggers, a task-based tool like Zapier may be easier to reason about, and self-hosted n8n can be cheaper at high volume if you can maintain it.
Make remains strong when scenarios have many steps, branching logic, and data transformation, because one run covers a lot of ground. Match the tool to the shape of your workflows.
Tips to Reduce Operation Costs
Filter early so runs stop before consuming unnecessary modules, and batch operations where possible instead of running one item at a time. Avoid polling triggers when a webhook can push data instantly.
Enable error handling so failed runs do not silently burn operations, and set scenario schedules to the slowest interval your task tolerates. Review the operations report monthly to spot wasteful scenarios.
Pros
- Operation-based pricing is cost-effective for multi-step scenarios
- Free plan lets you learn and test before paying
- Visual editor handles branching and complex logic well
- Pro and Teams add priority execution and collaboration
Cons
- Operation counting is confusing and can spike unexpectedly
- The free plan allows only one active scenario
- Complex looping scenarios can consume operations quickly
Frequently asked questions
What counts as an operation in Make?
Any module run that processes data counts as an operation. Multi-step scenarios consume several per run, so track usage carefully.
Is Make cheaper than Zapier?
Often for multi-step workflows, but not always. Compare based on your actual run volume and scenario complexity.
Can I use Make for free long term?
Only for lightweight automation. The free plan caps operations and allows a single active scenario, which is too little for regular business use.
When should I switch to n8n?
When you have high volume and technical skills. Self-hosted n8n can be cheaper at scale but requires maintenance.
Verdict
Start on Core if you run real automations, and upgrade to Pro or Teams only when scenario count or operation limits block you. Filter and batch aggressively to control operations, and consider n8n only if volume and technical capacity justify self-hosting.
