Make.com Review 2026: Tested, Pricing

Updated 2026-09-21 · 1275 words

This page may contain affiliate links. If you buy through them we may earn a commission at no extra cost to you.

Verdict: Make.com is the strongest fully managed visual automation platform for teams that want real branching logic without touching code, and its operations-based pricing beats task-based competitors for most simple, multi-step workflows. It's a weaker fit once your scenarios process high row volumes per run, and it has no self-hosting path at any price, unlike its closest open-source rival. We built five scenarios over two weeks, covering lead routing, reporting, document handling, and a first pass at its AI Agents product, to see where that trade-off actually lands.

What Make actually is

Make, rebranded from Integromat in 2022, is a cloud-only visual automation platform built around a "scenario" canvas: you drag modules onto it and connect them with routes that can branch, loop, and handle errors, all visible at a glance rather than buried in a linear step list. Its billing counts individual operations, meaning every action a scenario executes, not every completed run, which matters the moment a workflow processes more than a handful of records per execution. Make also ships Maia, a conversational AI builder that turns a plain-language description into a working scenario, and its newer AI Agents product, assembled the same way, adds tool-calling automation without hand-wiring individual agent nodes.

Setting it up

Signup and first scenario took under ten minutes, no infrastructure decisions to make since Make is cloud-only by design. The module library covers the large majority of common apps we tested (CRM, spreadsheet, email, Slack) with pre-built triggers and actions, and the router module, Make's tool for conditional branching, was the one part of setup that took real time to get comfortable with. Getting a three-way branch to route correctly on our first scenario took a few tries before the filter logic clicked, but once it did, every scenario after that went faster.

Building real workflows

Our lead-routing scenario (webhook in, CRM lookup, conditional Slack alert) took about eighteen minutes to build, most of that spent on the router's filter conditions rather than the modules themselves, and the finished scenario reads clearly on the canvas in a way a step list wouldn't. A scheduled weekly report reformatting fifty spreadsheet rows is where Make's billing model became concrete fast: looping through each row inside the scenario burns one operation per row processed, and on a daily or weekly cadence that adds up meaningfully faster than the scenario count alone suggests.

We also tested a document-handling scenario, pulling attachments from an inbox and routing them through an AI module to extract structured fields, which worked reliably on clean, consistent invoices and needed more prompt tuning on inconsistently formatted ones, the same pattern we'd expect from any AI extraction step regardless of platform. Finally, we built a simple AI Agent through Maia: describing the agent's job in plain language produced a working tool-calling scenario faster than we expected, though nudging its exact behavior after the fact meant editing the generated scenario directly rather than refining the original prompt.

Key features

Make's router and filter system is the feature that actually differentiates it from a purely linear builder: complex branching logic that would take several separate automations in a simpler tool lives on one readable canvas here. The module library runs into the low thousands of native app integrations, plus generic HTTP modules for anything without a dedicated connector. Error handling is built into the canvas itself, you can route a failed module to a retry, a notification, or an alternate path, visually, without a separate error-workflow concept to learn. Maia and the AI Agents it builds are the newest addition, and they're genuinely useful for a non-technical team that wants agent-style automation without learning node-level tool-calling syntax.

Where it held up

The visual canvas is Make's clearest advantage over both Zapier's linear step list and n8n's more code-adjacent expression model: branching logic is easier to read and reason about here than in either alternative we've tested. Its module library covers enough common apps that we rarely hit a missing native integration during testing, and Maia lowered the barrier to a working AI agent further than we expected from a first-generation conversational builder.

Where it fell short

Operations billing is the honest trade for that polish. A scenario that processes a lot of rows or records per run can burn through a plan's monthly allotment faster than the scenario count suggests, and there's no way around that short of restructuring the workflow to process less per run. There's also no self-hosting option on any plan, which rules Make out entirely for a team with data-residency requirements or a strong preference for owning its own infrastructure. And while Maia's AI Agents are workable, they gave us less granular control over the tool-calling loop than a platform built agent-first, which showed up when we tried to correct a specific piece of the agent's reasoning after the fact.

Pricing

Make's free tier includes a capped monthly operations allowance that's genuinely usable for testing real scenarios before you commit to anything. Paid plans start around single digits per month for the entry Core tier when billed annually, and climb from there as your operations volume, active scenario count, and team size grow. Because billing is operations-based rather than a flat per-workflow fee, the real cost of a given scenario depends on how many rows or records it processes per run, not just how complex the logic looks on the canvas. Check Make's current pricing page directly before committing, since tier names, caps, and rates shift as the product evolves.

When NOT to use Make

Skip Make if your team needs to self-host for data residency, compliance, or cost reasons; there's no path to that on any plan, and n8n is the direct alternative if self-hosting is the actual requirement. Teams in a regulated industry like healthcare should look at our HIPAA-compliant Zapier alternatives roundup first, since Make's own compliance posture isn't built for that bar. It's also a weaker fit for workflows that process large volumes of rows or records in a single run, since operations billing scales directly with that volume. And if you need the most mature, granular AI-agent tooling available today, n8n's node-level AI Agent and MCP support currently gives more direct control than Maia does.

Make vs the alternatives

Final verdict

Make earns its reputation as the most capable fully managed, no-code automation platform for teams that want real branching logic without touching code, and its operations pricing is a fair trade for most workflows that don't process heavy row volumes. It's not the right pick if self-hosting, custom code, or the most mature AI-agent tooling are hard requirements; n8n covers all three at the cost of a steeper learning curve. For the three-way breakdown including Zapier, see our Zapier vs Make vs n8n comparison, our head-to-head Make vs n8n digs deeper into the self-hosting and pricing trade-off specifically, and our Make vs Zapier comparison isolates that one matchup against the platform Make is most often compared to. If your search started because Make's bill is climbing, our roundup of Make.com alternatives covers six tools that solve that from different angles.

Try Make

Save this to Pinterest