Zapier, n8n, and custom code each win in different situations. The decision usually comes down to integration breadth, data residency, complexity of branching logic, and who will maintain the system.
The honest answer to “which workflow tool should we use” is “it depends”. The honest answer to “depends on what” is what most teams want to know. Here is how the decision actually looks when it lands on a real project.
Zapier wins, usually, when
The integration you need exists, the logic is straightforward, and the team that will maintain it does not have any technical comfort with self-hosted infrastructure.
Zapier’s strength is breadth. Their integration library is the largest in the category by a meaningful margin, and the long tail of less popular tools is where Zapier consistently has a connector and the alternatives do not. If your workflow connects, say, Notion to Buffer to a niche reservation platform, Zapier is the path of least resistance.
The other strength is non-technical maintainability. The interface is usable by non-developers, the templates are extensive, and the team you hand the system to can usually make small adjustments later without calling anyone.
The cost is the obvious trade-off. At any meaningful volume, Zapier becomes expensive fast. Workflows that fire frequently or process many records per run can land in the few-thousand-baht-per-month range easily. The pricing is also opaque enough that surprise bills are common.
n8n wins, usually, when
The workflow has more than three steps, involves any kind of branching, transforms data in non-trivial ways, or runs at a volume that would make Zapier expensive.
n8n is more flexible by design. Branches, loops, conditional logic, custom JavaScript inside nodes, all of this is more natural than in Zapier. The data model is less abstracted, which is sometimes a downside for non-technical users and almost always an upside once the workflow gets complex.
For Thailand-based businesses, n8n has a second advantage that does not get discussed enough. It can be self-hosted on infrastructure inside the country, which can matter for regulatory or data-residency reasons depending on the industry. Zapier and Make process data through their cloud, which is fine for most use cases but a non-starter for some.
The cost trade-off goes the other direction. n8n cloud is cheaper than Zapier for the same workflow load, often by a factor of two or three, and self-hosted n8n on a small VPS costs the price of the VPS, which is rarely more than a few hundred baht per month all in.
The trade-off is the team handling it. n8n is approachable but expects more comfort than Zapier. The non-technical maintainer who could keep a Zapier flow running without help may struggle to debug an n8n workflow that broke because a webhook source changed format.
Custom code wins, usually, when
The logic is specific to your business in ways no off-the-shelf tool covers. Or the volume is high enough that SaaS pricing would dominate the running cost. Or the workflow needs performance no platform delivers.
This is rarer than people think. Most workflows that feel like they need custom code can be implemented inside n8n with a small custom function node here and there, and the tooling savings (versioning, observability, a working interface, retry logic) make that the right choice. True custom code is the answer when the specific business logic is the differentiator and you want to own and maintain it as code rather than as a workflow file.
The downside is straightforward: someone has to maintain it. A custom workflow that runs on your own infrastructure is your responsibility forever. If your team does not include someone who will own that, do not build it.
The hybrid pattern
In practice, most builds we ship are hybrid. The orchestration sits in n8n. The LLM calls go directly to the model API. A handful of complex steps are written as custom code and called by n8n as if they were standard nodes. Where Zapier has a unique integration that would be expensive to build from scratch, we sometimes use Zapier just for that single connection and pipe its output into the rest of the system.
This is rarely a discussion point in the sales conversation. It should be. The vendor that walks you through which steps live where, and why, is the one that has thought about the engineering rather than just the sales pitch.
The decision shortcut
If you remember three things from the comparison:
- Zapier wins on integration breadth and ease of non-technical maintenance.
- n8n wins on flexibility, cost at scale, and data residency.
- Custom code wins when the business logic is the differentiator and you have the team to own it.
If you do not have a strong preference, n8n is the right default for most SME workflows in Thailand. The cost is reasonable, the flexibility is there when you need it, and the data stays where it makes sense.
The wrong move, in either direction, is to pick the tool first and force the workflow into it. The workflow should drive the tool choice, not the other way around.