n8n, Make, Zapier or code: how a buyer chooses

The short answer

You do not have to choose the tool before you hire. A good seller will recommend one. But you should know which of five questions decide it, because the answer changes what you are left with when the seller has moved on:

1. Who will look after it once the freelancer is gone?
2. How often does it run, and how much does each run move?
3. What does it connect to: popular apps, your own systems, or a website behind a login?
4. Where may the data go: is a third-party cloud acceptable?
5. How much logic is in it: a straight line, or many branches and exceptions?

Roughly: Zapier when a non-technical team will own it and volume is modest. Make when there is more branching logic and volume, and you still want a visual tool someone else hosts. n8n when volume is high, data should stay on your infrastructure, or you want to avoid per-run charges, and someone can keep a server running. Custom code when the job needs what the platforms do poorly, and someone can read code later.

What each option leaves you owning

The build ends. This is what stays with you.

Non-technical team, modest volume

Zapier

A hosted account and a usage bill that grows with volume.

More branches and volume

Make

A hosted account, with scenarios a technical user can follow.

High volume, data in-house

n8n

A server (or cloud plan) someone must keep running and updated.

Local files, logged-in browsers

Custom code

Code only a developer can change, and wherever it runs.

See the options as a table

Option	Usually fits when	What you are left owning
Zapier	A non-technical team owns it; modest volume; popular apps	A hosted account and a usage bill that grows with volume
Make	More branches and volume; still a visual tool someone else hosts	A hosted account; scenarios a technical user can follow
n8n	High volume, data kept in-house, or no per-run charge wanted	A server (or cloud plan) someone must keep running and updated
Custom code	Local files, logged-in browsers, heavy processing	Code only a developer can change, and wherever it runs

Why this is harder than it looks

Sellers have favourites, and a seller who only builds in one tool will recommend that tool. That is not dishonest; it is what they know. Your job is to check that the recommendation fits your answers to the five questions, not theirs.

The comparison articles online compare features. For a buyer, the feature lists are close enough. What differs is the cost of owning it for two years: the monthly bill as volume grows, and the cost of fixing it when something changes.

What I learned from running everything as code

All of my own automations are custom code: scripts on my own computer, started by the operating system’s scheduler. Around two dozen of them publish posts, collect data and send me alerts. I chose code because an AI coding tool writes it quickly, and because several jobs need things the platforms handle poorly: files on my disk, a browser that stays logged in, custom processing.

It works, and it has costs I would warn any buyer about:

• The machine has to be awake. Scheduled runs were delayed or silently skipped while my computer slept. A hosted platform does not have this problem; a home machine or an unmanaged server does.
• Every failure is mine to notice. Platforms show a run history, and most can alert you when a run fails, some with a little setup. My scripts needed their own alerts and a separate watchdog, and even then one job stopped quietly for two days when a login token expired, because the watchdog was not checking for that.
• Only someone who reads code can fix it. That person is me, with the same tool. A business handing custom code from a freelancer to a non-technical team is handing over something nobody on the team can open.

The last point is the one that decides most cases. The acceptance checklist is written from the first two.

What a hosted platform does that my scripts had to do themselves

Around two dozen scheduled scripts on my own computer.

Hosted platformMy scripts Runs while my computer sleeps ✓ yes✗ delayed or skipped Shows a run history ✓ built innot built in Alerts when a run fails ✓ most, some setupown alerts + watchdog Who can fix it visual screensonly someone who reads code

The five questions, and what each answer points to

1. Who will look after it? If nobody on your side will ever open it, choose the option with the clearest screens and run history, and a large pool of other freelancers who know it. Zapier and Make both qualify. If you have a technical person, n8n and code open up.

2. How often does it run? Hosted tools charge by usage: tasks on Zapier, operations or credits on Make, executions on n8n’s cloud plans. A workflow that runs a few hundred times a month costs little anywhere. One that processes thousands of items a day can make the per-run model the biggest line in the budget, which is where self-hosted n8n or code start to pay off. Ask the seller to estimate your monthly usage and the bill that goes with it, on your account.

Every hosted tool bills by usage, under a different name

Zapier counts

Tasks

Make counts

Operations or credits

n8n cloud counts

Executions

Self-hosted n8n: no per-run charge.

A few hundred runs a month

Per-run bill→costs little anywhere

Thousands of items a day

Per-run bill→can be the biggest line in the budget→self-hosted n8n or code start to pay off

3. What does it connect to? Popular apps with official integrations are easy on every platform. Your own database or an internal system is easier with n8n or code. A website with no API, behind a login that expires, is hard for everyone. That may be a sign it should not be automated first; see what to automate first.

4. Where may the data go? Zapier and Make run in their cloud. n8n can run on your own server, and code can run wherever you put it. If customer or financial data should stay in-house, that decides it before price does.

5. How much logic? A straight line (when a form arrives, add a row, send a message) suits any tool. Many branches, loops and exceptions get awkward in the simplest visual builders; Make and n8n handle more of it visually, and code handles anything, at the cost of question 1.

Where your answers point

✓ = the article points this way for that answer. Not a score.

ZapierMaken8nCode 1. Nobody technical will look after it ✓✓needs a tech personneeds a tech person 2. Thousands of items a day bill growsbill grows✓ self-hosted✓ 3. Your own database or internal system ——✓ easier✓ easier 4. Data must stay in-house their cloudtheir cloud✓ your server✓ where you put it 5. Many branches and exceptions —✓✓✓ anything

Where it goes wrong

• Choosing on the build price. The cheapest build can be the most expensive tool to run at your volume, or the hardest to hand over.
• The platform account is the seller’s. Whatever the tool, the account it runs on should be yours, with the seller given access you can remove. Otherwise their cancelled subscription is your outage.
• Self-hosting without an owner. n8n on a server is cheap until the server needs an update and nobody is responsible. Put that in the maintenance terms.

Wrap-up

Write your answers to the five questions into the brief, not a tool name. Then ask each seller which tool they would use and why, and what it will cost per month at your volume on your account. The seller whose answer uses your five answers is the one who understood the job. The brief template on the workflow automation page has room for all of it.

Put answers in the brief, not a tool name

1. Answer the five questionsWho looks after it, volume, connections, data, logic.
2. Ask each sellerWhich tool, why, and the monthly cost at your volume on your account.
3. Pick the one who used your answersThat seller understood the job.