By KYN AI Advisory Team — AI implementation specialists, Singapore
Use Zapier to connect two or three apps fast at low volume. Use n8n when you need branching logic, self-hosting or higher volume at a lower unit cost, and you have someone who can maintain it. Use custom code when the workflow moves money, files with an authority, or must leave an audit trail you own. Most SMEs end up with a mix. The skill is knowing where each tool stops.
What is the difference in one table?
| | Zapier | n8n | Custom code | |---|---|---|---| | Who builds it | Anyone on the team | Technical operator | Engineer | | Hosting | Zapier's cloud | Your server or n8n's cloud | Your cloud account | | Pricing unit | Tasks per month | Executions, or free if self-hosted | Build fee plus run cost | | Branching and loops | Paths, limited | Strong, visual | Unlimited | | Audit trail you own | Task history in the tool | Execution log, yours if self-hosted | Designed to your needs | | Time to first working flow | Hours | Days | Weeks | | Failure handling | Basic retries and alerts | Error workflows | Designed per case | | Who maintains it | The builder | The builder | Contract or in-house |
The table hides one thing: the cost of a tool is not its price. It is the price plus the hours someone spends fixing it when an app changes its fields.
When does Zapier fit?
Zapier fits when the flow is short, the volume is low and a failure costs little.
Examples that fit: a form submission creates a row in a sheet and posts to a chat channel; a new paid invoice sends a thank-you message; a calendar booking adds a contact to a list.
Zapier's pricing page shows the model. The free plan includes 100 tasks a month. The Professional plan starts at 750 tasks a month at US$19.99 a month on annual billing, and higher tiers scale with task count. Failed actions, triggers and built-in tools such as Formatter and Paths do not count as tasks, and some steps, including AI steps and MCP calls, cost more than one task. Checked 30 October 2026.
The implication: the bill follows volume. A flow that runs 50 times a day uses roughly 1,500 tasks a month for every action step in it. Multiply by the number of steps before you choose a tier.
Where Zapier struggles: long flows with many branches, flows that need a database of their own, and anything where you must prove later who did what.
When does n8n fit?
n8n fits when you want more control than Zapier gives and have someone technical to run it.
Three differences matter:
- Self-hosting. n8n's documentation states that self-hosted installations run on the same underlying product, and that you can run the free Community edition without a license key or buy a Business or Enterprise plan. Your data then stays on a server you choose.
- Logic. Branches, loops, merges and sub-workflows are first-class. A flow with ten decision points stays readable.
- Unit cost. Self-hosted, you pay for the server, not per task. At high volume this is often the cheapest of the three.
The trade-off is operations. Someone patches the server, backs up the database, rotates credentials and reads the failure alerts. If that someone is a founder who does it on Sundays, the saving is not real.
Check the licence terms for your use before you build a product on it. Read the current text on n8n's site, because terms differ between the free edition and paid plans.
When does custom code fit?
Custom code fits when the workflow carries risk or must scale in a way a visual tool will not.
Four signals:
- It moves money. Payments, refunds, payroll, supplier bank changes.
- It sends in your name at volume. Outbound email or WhatsApp where a mistake reaches hundreds of people.
- It needs row-level permissions. Different staff see different records, and the rule is enforced in the database.
- It must be audited. Every action logged with the actor, retained for years, searchable.
Visual tools can do parts of each. They do them with shared credentials, flat permission models and logs inside the vendor's console. That is acceptable for a newsletter signup. It is not acceptable for a payment run.
Custom code also removes a hidden limit: you are not bound by a connector catalogue. If your supplier has an odd API or your ERP is old, you write the adapter once and own it.
The price is real. A build costs more than a subscription, and a change needs an engineer. Include that in the comparison honestly.
What does each option cost to run?
Compare on three lines, not one.
- Licence or run cost. Per-task, per-server, or cloud usage. Easy to price.
- Build and change cost. Hours to build, hours per change. Often larger than the licence.
- Failure cost. What one wrong run costs. A wrong thank-you message costs nothing. A duplicate supplier payment costs the payment, plus the time to recover it.
Rule of thumb: when failure cost is high, spend on build quality. When failure cost is near zero, spend on speed.
How do you decide for a specific workflow?
Ask five questions of each workflow, in order.
- Does it move money, file or delete? If yes, custom code or a tool behind an approval step.
- Does it run more than a few hundred times a day? If yes, price n8n self-hosted or custom code, not per-task pricing.
- Do you need to prove who did what? If yes, you need logs you own.
- Is there a person who will maintain it? If no, use the tool with the least to maintain, or buy maintenance.
- Will it change often? If yes, favour a visual tool for the changing edge and code for the stable core.
A common and sound pattern: Zapier or n8n at the edge, where a form or a calendar triggers something, and custom code in the core, where records are written and approvals are held. The edge tool calls the core through one authenticated endpoint. Swapping the edge tool later changes nothing inside.
Where KYN fits
KYN builds the core: the system of record, the agents and the approval steps, in a cloud account in your name. We do not replace a visual tool that is doing its job. In the review, which takes the first 14 days, we inventory your current flows and mark each as keep, move or retire. A full build ships in under 90 days.
One example is a manufacturer whose eleven systems became three on a single AWS account, with a 06:30 report to each department on WhatsApp at about S$0.05 per report. Outbound messages, money, filings and deletions wait for a named person, and every action is logged with the actor. See integrations and infrastructure. For a related comparison, read custom WhatsApp system vs off-the-shelf tools.
Frequently asked questions
Is n8n free?
The Community edition can be self-hosted without a license key, per n8n's documentation. You still pay for the server and the time to run it. Paid plans add features and support.
Can I start with Zapier and move later?
Yes, and it is a sound way to learn what the process is. Keep a written list of each flow, its trigger, its steps and its owner, so a later move is a rebuild from a specification and not a guess.
Do I need custom code for AI agents?
Not for a simple draft or summary step, which a visual tool can call. You need it when the agent acts: sends, posts, pays or deletes. Those actions need approval gates, restricted accounts and logs that a visual tool does not give you by default.
Checked 30 October 2026.
Curious whether Marketing agents fits your business? Talk to KYN on WhatsApp — no forms, just a conversation.
