Zapier, Make, or n8n, or a custom build?

What are you actually choosing between?

A small business owner posted this exact question on r/smallbusiness: stitch it together on a no-code stack, buy an off-the-shelf tool, or have someone build a custom solution. Three options, one budget, no obvious way to compare them.

The first thing to say is that the third option is not what most people picture. A custom build is usually not a from-scratch codebase that replaces Zapier. A large share of what agencies deliver, including a large share of what we deliver, runs on Zapier, Make, or n8n underneath, with custom code filling the gaps the platform can’t reach. The real choice is not no-code versus code. It is who designs, secures, and maintains the thing once it exists.

Hold that thought, because it is the only variable that reliably predicts which option is right for you.

When is Zapier, Make, or n8n the right answer?

When all of these are true:

• You have one to three workflows, and they’re simple and stable. Trigger, a couple of steps, done.
• Nothing in the chain is business-critical at 2am. If it silently breaks on a Friday, you find out Monday and nothing is on fire.
• Someone in-house is technical enough to build it and willing to own it next quarter, and the quarter after that.
• The systems involved don’t hold anything you’d have to disclose if it leaked.

If that’s you, buy the tool. Make’s Core plan is $12/mo, Zapier Pro is $19.99/mo, n8n Starter is €20/mo, and self-hosted n8n is free if you already run infrastructure. A $10K–$20K build is genuinely overpriced for that job, and any agency that tells you otherwise is selling you something you don’t need.

That price gap is real, and we don’t pretend it isn’t.

How do the three differ?

	Best for	Price shape	The catch
Zapier	The widest integration coverage, non-technical builders	Free, then $19.99/mo Pro, $69/mo Team; metered by task	SSO and audit logging are gated to the higher tiers
Make	Complex, branching, data-heavy workflows	Free, then $12/mo Core up to $38/mo Teams; metered by credit	The visual canvas has a real learning curve; credit metering arrived in August 2025 and expiring credits confuse the bill
n8n	Technical teams who want to self-host	Free self-hosted, then €20/mo Starter to €667/mo Business; metered by execution	Self-hosting hands you the entire security surface

Two things this table doesn’t show. First, the entry price is not the bill: all three meter usage, and AI steps consume more of the meter than plain ones. Second, none of the three ships an outcome guarantee, because none of them is selling you an outcome. They’re selling you a tool. That’s a fair trade, but it is worth naming.

Where does a no-code stack stop being enough?

Four failure points, in the order we usually see them.

1. Nobody owns it. The person who built the Zaps changes role, or gets busy, or leaves. The automation keeps running until an API changes, and then it doesn’t. This is the most common one by a wide margin, and it has nothing to do with the tool’s capability.

2. You add an AI step and lose determinism. Zapier’s own documentation concedes that its AI agents won’t give the same outcome every time. That’s an honest disclosure, and it’s fine for drafting a summary. It is not fine for deciding which customers get refunded. The moment an AI step makes a decision that costs money, you need approval gates and an audit trail, and the platform will not design those for you.

3. The meter surprises you. Task, credit, and execution metering all behave the same way: cheap while you’re experimenting, and then not, once the workflow runs on real volume. Make’s switch to credits in August 2025 is the clearest recent example of a pricing model changing under people who had already built on it.

4. The security surface becomes yours. This is sharpest with self-hosted n8n, which is otherwise the best-value option in the category. Self-hosting means you own secrets management, patching, network isolation, and prompt-injection containment for a system holding credentials to your CRM and your billing. For a team with a platform engineer, fine. For a team without one, that’s a liability sitting quietly in a container.

What does a custom build actually buy you?

Not better software. Be clear-eyed about this. What you’re buying is:

• Someone else owns it. Design, build, integration, and the decisions about what happens when an API changes.
• Guardrails designed in from the start. Scoped access rather than an admin API key, audit logging of what the agent did, and a human approval gate on any write that costs money or touches a customer.
• A success metric agreed in writing before work starts, so “did this work” has an answer that isn’t a feeling.
• A fixed scope where someone else carries the overrun, if the vendor sells that way. Many don’t.

And what it does not buy you: a lower monthly cost, a system that never needs attention, or exotic technology. If those are the pitch, be suspicious.

Isn’t that just the same tools with a bill attached?

Partly, yes, and we’d rather say so than have you find out later. The platforms under a custom build are frequently the ones you could have bought yourself. The work you’re paying for is the design, the integration into your actual stack, the guardrails, and the accountability for whether it hits a number.

That framing also gives you a good test for any vendor. Ask what their build runs on. A straight answer names real platforms and where custom code picks up. A vague answer about a proprietary engine usually means Make with a logo on it, and a markup you can’t inspect.

So which one do you need?

Work down this list and stop at the first “no”:

1. Are the workflows simple and stable? If no, a no-code stack will keep breaking regardless of who builds it.
2. Will someone in-house own it a year from now, by name? If no, you are buying a maintenance problem, not an automation.
3. Does it touch customer data, money, or anything with a compliance obligation? If yes, guardrail design is the job, not a feature of it.
4. Is the cost of the manual work bigger than the cost of the build? If no, don’t build it yet.

Most companies that reach step four already know the answer. The ones that stall are usually stuck on step one, because nobody has actually mapped the workflows in enough detail to tell whether they’re simple or not.

That mapping is the thing worth buying first, and it is a much smaller purchase than a build.