n8n and Make are workflow builders with an AI-agent node bolted on; a custom agent is code that calls a model with your tools, your rulebook and your tests. Use Make when a non-technical person will own a simple flow and the AI step is a summary or a classification. Use n8n when someone technical will own it, you want to self-host, and the agent is internal or low-stakes. Build a custom agent when it talks to customers, writes to a system of record, or has to pass a test set before every change, because the approval step, the audit log and the sixty-message test are the product, and the builders make those hard. Most good setups use both: the builder for the plumbing and a custom agent for the part that needs reading and deciding.
All three can run something that looks like an agent in a demo. They differ on who can change it, what happens when a message does not fit, what you can prove about it afterwards, and what it costs at your volume. This page puts them side by side on those, says which fits which business, and shows the arithmetic for a month of a clinic’s bookings on each.
| Make | n8n | Custom agent | |
|---|---|---|---|
| What it is | Hosted visual workflow builder, per-operation or credit billing | Visual workflow builder, hosted or self-hosted, per-execution billing | Code calling a model API with your tools, rulebook and tests, on your own hosting |
| Who changes it | An operations person, no code | A technical person; some JavaScript helps | A developer; the rulebook and facts list are edited by the business in a sheet |
| AI agent support | An AI agent builder on the same canvas; good for a summary or a classification step | An agent node with tools, memory and model choice; capable, with care | Whatever the model API supports: strict tool schemas, structured output, caching |
| Tool permissions | Each module does one thing; "may do alone / with approval" is yours to wire | Tools are workflows or nodes; permissions are what you wire | The tool list is the permission list, by construction |
| Approval step | Possible with a human-in-the-loop module or an email; clumsy at volume | Possible with a wait node and a form; workable | Built in: draft, approve, act, with the queue in your console |
| Audit log | Execution history per scenario, retained by plan | Execution data per run, retained by setting; self-hosted keeps everything | Every message, tool call and decision in your own table, forever |
| Test set before a change | Manual re-runs | Manual or scripted re-runs | The sixty-message set runs in CI before every change |
| Multi-turn WhatsApp conversation | Awkward: state lives in a data store module | Workable with a database node | Native: the conversation is the unit |
| When it breaks | A renamed field, an unexpected branch, an operation cap | The same, plus the server if you self-host | Rules nobody wrote; data it cannot reach |
| Cost model | Per operation or credit, monthly plans | Per execution on cloud; free to self-host, you pay for the server | Model usage plus hosting; the build is a fixed fee |
| Cost at 2,000 agent conversations a month | A mid plan, likely tens of dollars, plus model usage; worked below | A starter cloud plan or a small server, plus model usage; worked below | Low hundreds of dollars at most, usage and hosting; worked below |
| Data location | Make’s cloud regions | Your server if self-hosted | Your hosting and your model vendor’s region |
| Lock-in | Scenarios do not export to anything else | Workflows export as JSON; self-hosting is portable | Plain code and schemas; the model is swappable |
When an operations person will own the flow, the AI step is a summary or a sort, and nothing talks to a customer unsupervised. It is the fastest way from a form to a CRM to a Slack message, and the visual canvas is the right tool for that.
When someone technical will own it, you want the data on your own server, and the agent is internal: a morning summary, a document check, a draft for a person to send. It is also the right place to prototype an agent before deciding whether it deserves code.
When the agent is customer-facing, writes to a system of record, or has to pass a test set before every change. The approval queue, the audit log and the test run are easy in code and awkward on a canvas, and they are what makes a clinic or a CA firm safe to run one.
Both builders now have an agent node: give it a model, a prompt and some tools, and it loops until it is done. For an internal task that is enough, and it is a genuinely good way to find out whether a workflow is agent-shaped before spending on a build. The reference builds on this site were all prototyped that way.
What the node does not give you is the scaffolding that makes an agent safe on real customers. An approval queue someone works from a screen. A log you can filter by patient. A test set of sixty awkward messages that runs before every rule change and fails loudly. Strict tool schemas so a booking call cannot arrive without a date. A rulebook the practice manager edits in a sheet rather than in a prompt box only the builder can see. Each of those can be wired on a canvas; together they are more work than the code, and they break in ways a canvas does not show.
Take the clinic reference build: about 2,000 booking conversations a month, four turns each. On a builder each turn is a handful of operations (receive, load rules, call the model, call a tool, reply, log), call it six, so a conversation is roughly 25 operations and a month is roughly 50,000. On a custom agent the same month is model usage plus hosting. The build fee for the custom option is a one-off and is shown separately so the comparison is honest.
| Option | What the month consumes | Monthly running cost | One-off build |
|---|---|---|---|
| Make | About 50,000 operations or the credit equivalent | A mid-tier plan: described on Make’s pricing page; tens of dollars at this volume, more if AI steps cost extra credits | Your time, or a freelancer’s day rate |
| n8n cloud | About 2,000 executions (one per conversation) | A starter plan covers it: described on n8n’s pricing page | Your time, or a freelancer’s day rate |
| n8n self-hosted | The same, on your own server | A small VPS, typically under $20, plus someone’s hours for updates and backups | Your time, plus the server setup |
| Custom agent | About 28M input and 4M output tokens before caching, plus a database and a host | $120–$600 a month: the estimator’s mid-volume band, model usage before caching plus hosting | $4,500 for the pilot; $8,000–$42,000 for one workflow in production |
The setups we are happiest with are not one of the three. Make or n8n watches the form, the inbox and the calendar and moves records between them, which is what they are superb at. The agent is a small service behind a webhook that reads the message, applies the rulebook, calls its five tools and writes the log, and the builder calls it like any other node. The business keeps a canvas it can see; the part that needs tests and an approval queue lives in code; and if the builder is ever replaced, the agent does not notice.
It also keeps the agent small, which is what keeps it auditable. An agent asked to do everything on one canvas is the thing nobody can explain to the doctor who asks what it did last Tuesday.
Answer them in order. Most people are done by the third.
Will the agent talk to customers or write to a system of record without a person in between?
Yes: Custom agent, with the builder for plumbing if you have one. Continue to check the rest.
No: A builder is fine. Continue.
Is there someone technical who will own a server and a workflow?
Yes: n8n, self-hosted if data location matters.
No: Make, hosted.
Will someone ask to see the log, by customer, months later?
Yes: Custom agent, or n8n self-hosted with a database node and retention set to keep everything.
No: Any of the three.
Do the rules change often, and should a non-developer change them?
Yes: Custom agent with the rulebook in a sheet, or a builder with the rules in a sheet the node reads. Not a prompt box.
No: Continue.
Is the volume above a few thousand conversations a month?
Yes: Run the cost table with your numbers; operation-based plans climb fastest.
No: Cost is tens of dollars on all three. Decide on ownership and auditability instead.
Yes, and it is a good path. Prototype the agent on n8n with the rulebook in a sheet, learn the edge cases from a few weeks of real messages, then move the brain into code with the test set those weeks produced, keeping n8n for the plumbing around it. The pilot can start from exactly that point.
Not to run. Model usage is the same on a builder, because the agent node calls the same API; a custom agent adds a database and a host that cost tens of dollars at small-business volume, and skips the plan fee. The difference is the build, which is a fixed fee against a brief, and the maintenance, which is a person either way.
The one where you can say, in two lines, where the data goes. Self-hosted n8n and a custom agent on your own hosting make that easy. Make and n8n cloud put it in the vendor’s region under the vendor’s agreement, which is fine for many businesses and not for some. The model vendor’s region applies to all three.
We use both for plumbing in client setups and recommend them by name; we build the agent itself in code because the approval queue, the audit log and the test run are what we are being paid to make safe. If a workflow does not need those, we will say so and point you at the builder.
Zapier belongs in the same column as Make: hosted, visual, task-based pricing, an AI step available, the easiest for a non-technical owner. The agent-vs-chatbot-vs-Zapier page covers the broader question of whether you need an automation or an agent at all.
For a technical owner who wants to self-host and build an internal agent, n8n; for a non-technical owner who wants hosted plumbing with one AI step, Make. n8n’s per-execution billing is cheaper on multi-step workflows and its workflows export as JSON; Make’s canvas is easier to pick up and its per-operation or credit billing climbs faster at volume. Both prices change often; read the vendors’ pages on the day.
The self-hosted community edition is free to run on your own server; you pay for the server and for someone’s hours to keep it updated and backed up. n8n cloud is a monthly subscription billed per execution, described on its pricing page. Model usage for an agent node is billed by the model vendor on top in either case.
Yes. Its agent node takes a model, a prompt and tools and loops until done, which is enough for internal agents and a good way to prototype a customer-facing one. What it does not give you out of the box is the approval queue, the per-customer audit log and the test set that runs before every change, which is why customer-facing agents usually end up with the builder doing the plumbing and the brain in code.
Free, no deck. You leave with an approach, a timeline and a price range, or a reason to buy something off the shelf instead.