n8n vs Zapier vs Make: Which Automation Engine Fits Your SMB

Pick the wrong automation platform and you'll either bleed cash on per-task fees or stall out on workflows your tool can't handle. Zapier, Make, and n8n all move data between apps, but they price, scale, and lock you in very differently. Here's how to choose without getting talked into the wrong tier by a sales rep.

The Three Tools Solve the Same Problem Differently#

Zapier is the path of least resistance. You connect two apps, define a trigger and an action, and it runs. The interface is linear, the app catalog is the largest of the three, and the learning curve is measured in hours. You pay per task — every action step in every run counts against your monthly quota.

Make (formerly Integromat) gives you a visual canvas with branching, iteration, and data manipulation that Zapier hides behind paid tiers. You pay per operation, which is roughly each module execution. Operations are cheaper than Zapier tasks, so the same workflow usually costs less to run — but the editor demands more from you. If you've never thought about arrays, routers, or aggregators, expect a real ramp.

n8n is the outlier. It's open-source, node-based, and you can self-host it on a $10/month VPS or use their cloud. Pricing on the cloud plan is per workflow execution, not per step, so a 40-node workflow costs the same as a 2-node one. Self-hosted, it costs whatever your server costs. The catch: you're now running infrastructure, or paying someone who can.

Cost Math That Actually Reflects Reality#

The pricing pages lie by omission. Here's what matters.

Zapier's quoted task count assumes clean, single-step automations. Real workflows include filters, formatters, paths, and lookups — each one a task. A "sync new Stripe customer to HubSpot and Slack" flow isn't 1 task per customer; it's often 4-6 once you add deduplication and formatting. At the Professional tier, you hit the ceiling faster than the marketing suggests.

Make's operations model is more forgiving for complex flows, especially anything that loops over rows or items. A workflow that processes a 50-row spreadsheet burns 50+ operations in Make but can chew through hundreds of tasks in Zapier. For data-heavy work, Make is typically 3-5x cheaper at equivalent volume.

n8n self-hosted breaks the per-execution model entirely. If you're running 100,000 executions a month, your cost is still the VPS bill. The breakeven point against Zapier's Team plan lands around 10,000-15,000 monthly tasks for most SMBs. Below that, the operational overhead of self-hosting isn't worth it. Above it, n8n pays for itself in the first quarter.

The Complexity Ceiling Is Where Tools Actually Fail#

Every automation platform handles the happy path. The question is what happens when you need conditional logic, error handling, custom API calls, or AI model orchestration.

Zapier's ceiling is low and obvious. Paths (its branching feature) are clunky, Code steps run JavaScript or Python in a sandbox with tight limits, and debugging multi-step workflows means clicking through history one run at a time. For workflows under 5 steps with mainstream apps, it's fine. Past that, you'll fight the tool.

Make handles complexity better. Routers, iterators, and aggregators let you build real data pipelines. You can call arbitrary HTTP endpoints, manipulate JSON, and chain dozens of modules without the UI collapsing. The ceiling appears when you need version control, environment separation, or sophisticated error recovery — Make has rudimentary versions of these, but they're not built for teams shipping production automations.

n8n has effectively no ceiling for SMB use cases. Custom JavaScript or Python in any node, native LangChain integration, queue mode for scaling, Git-backed workflow files, and a code-first escape hatch whenever the visual editor gets in the way. The tradeoff: that power makes simple things slightly harder. A "new lead to CRM" flow takes 5 minutes in Zapier and 15 in n8n.

Lock-In Is the Hidden Cost Nobody Quotes#

This is where the conversation usually ends, and it shouldn't.

Zapier owns your workflows. You can't export them in any meaningful format, you can't run them outside Zapier, and you can't migrate them programmatically. If Zapier raises prices 40% — as they have, repeatedly — you either pay or rebuild from scratch. Their pricing has trended steadily upward since 2019, and the free tier has gotten thinner each year.

Make is in the same boat structurally, though their pricing has been more stable. Scenarios are stored in their format, on their servers, and migration tools don't really exist.

n8n workflows are JSON files. You own them. You can version-control them in Git, move them between self-hosted and cloud instances, fork the platform if you need to, and run them on your own hardware indefinitely. If the company disappeared tomorrow, your automations would keep running. For any business building automation as a core operational layer, this matters more than the monthly bill.

How to Actually Decide#

Forget feature matrices. The decision comes down to three questions.

How many monthly executions will you run in 12 months? Under 2,000, Zapier is fine and the time savings of its simpler UI outweigh the cost. 2,000 to 15,000, Make is usually the sweet spot. Over 15,000, or anything involving heavy data processing, n8n self-hosted wins on cost alone.

Who maintains the workflows? If it's a non-technical operator and you have no dev resources, Zapier. If it's a technical founder or ops person comfortable with JSON and basic scripting, Make or n8n. If you have or are willing to hire someone who can manage a small server, n8n unlocks a different category of work.

How critical is the automation to revenue? For workflows that touch billing, order fulfillment, or customer communication, the ownership question matters. Renting your operational backbone from a vendor that can change terms quarterly is a real risk. For internal nice-to-haves, who cares.

Most SMBs we work with end up running a mix. Zapier for quick one-offs that non-technical staff own. n8n self-hosted for the 5-10 workflows that actually run the business. Make occasionally as a middle ground when the team isn't ready for self-hosting but Zapier's pricing has gotten absurd.

The wrong move is picking one tool because a YouTube comparison told you to. The right move is matching the tool to the workflow's volume, complexity, and criticality — and being willing to run more than one.

If you want help auditing which automations belong on which platform, and what migrating off Zapier would actually cost you, see how we work.