Zapier vs Make vs n8n for Australian businesses (2026): with the AU tools nobody else covers

All three connect your apps and move data between them without you writing glue code. The difference is the pricing model and where the software runs. Zapier is a cloud service with the largest app catalogue of the three. It prices by task, meaning each action step that runs counts against your plan (source: zapier.com/pricing). Make, formerly Integromat, is a cloud service with a visual scenario builder. It prices by operation, so a multi-step scenario can consume several operations per run (source: make.com). n8n is open-source and self-hostable. You can run it on your own server for the cost of that server, with no per-task or per-operation meter. It also offers a managed cloud plan priced by workflow executions rather than per task (source: n8n.io). That last distinction is the one Australian businesses should care about most, and it is the one every other comparison skips. Zapier and Make run on vendor servers and you do not own the running system or control where the data lives. Self-hosted n8n you own outright, including data residency.

Zapier, in most cases. If you are a sole trader wiring up a handful of simple connections, such as a form submission creating a contact and sending a confirmation, Zapier's catalogue and setup speed win. You will hit the per-task meter eventually, but a solo operator running low volumes usually stays cheap. Make is the better pick the moment your workflows get multi-step and higher volume, because its per-operation model can work out cheaper for complex scenarios than Zapier's per-task one. It has a steeper learning curve. The real trap for solo operators is not the tool. It is buying any of them, half configuring it, and letting it become shelfware because you are the only person who understands it and you are already flat out.

This is where the per-task and per-operation meters start to bite. A workflow that fires hundreds of times a day is cheap to build and expensive to run on Zapier or Make. Two options are sensible. If your team wants zero server maintenance and someone reliable to phone, stay on cloud Make or Zapier and accept the metered cost as an operating expense. If you have any technical capability in-house, self-hosted n8n removes the meter entirely. You pay for a server, not for every step. At volume, that difference compounds. There is a real counter-argument here. Self-hosting means someone has to run the server, apply updates and fix it when it breaks. That is a genuine cost, and if nobody on your team can or will do it, cloud is the honest answer. The point is to choose with eyes open, not to chase the cheapest sticker.

Self-hosted n8n. If you handle health records, financial data, legal files or anything covered by the Australian Privacy Principles, where your data physically lives and who can access it becomes a real question. Cloud automation tools route your data through their own infrastructure, typically hosted overseas. Self-hosting n8n lets you run the whole thing on infrastructure you control, including an Australian cloud region, so customer data does not leave systems you administer. This is not legal advice, and self-hosting alone does not make you compliant. But it removes the awkward conversation about a US vendor processing your clients' personal information, and it gives you a defensible answer when a client or auditor asks where the data goes. Note that reforms to the Privacy Act, including rules around automated decision-making, are tightening (source: keypointlaw.com.au). Owning where your automations run is cheap insurance.

This is the question every generic comparison ignores, and the honest answer is that it varies, so check before you commit. Xero is widely supported. Zapier and Make both list Xero integrations, so accounting workflows are usually straightforward. MYOB, ServiceM8, Tradify, Deputy, simPRO and Cin7 are more hit and miss. Some have native connectors in one or more of the three tools; others you reach through the tool's own API or webhooks, and native support changes over time, so check each tool's current listing before committing. Here is the practical rule. If your AU trade or SMB tool has a public API, and most of these do, then n8n can talk to it through generic HTTP requests even when no polished connector exists. That flexibility is a quiet advantage of the self-hosted route: you are never blocked because a vendor has not built a connector for a tool that is common in Australia but niche globally. Australian trades operators already feel the gap in their own software. As trades operators put it in the research corpus, the options are a notepad or bloated overkill at around one hundred and fifty dollars a month, with nothing in the middle. The typical AU trade stack is ServiceM8 plus Xero, sometimes Tradify, held together by hand. Automation between those tools is exactly the seam worth closing, and it is a seam offshore competitors rarely map correctly.

Yes, if you host it in an Australian region on infrastructure you control. When you run n8n on your own server, the workflow data is processed there rather than on a vendor's servers. Choose an Australian cloud region or an on-premises machine and the data stays onshore. The trade-off is ownership of the running system, in both directions. You own where the data lives, and you also own keeping the server patched and available. For a data-sensitive business that is usually the right trade, because the alternative is trusting an overseas vendor with information you are legally responsible for.

No, and this is the most important part of the whole comparison. Australian owners burned by vendors already sense this. One described sellers quoting businesses like his dad five or six figures for what sometimes is just a GPT wrapper, as a poster put it on r/ausbusiness. The five figures does not buy a better tool. It buys a dependency. Builders who do this for a living say the same thing about the tools themselves. On r/zapier, one put it bluntly: every single failure is a mapping failure, nobody breaks automations because they picked the wrong tool. Another, on r/n8n, reported the number worth remembering: they built over forty automations in their first year and maybe ten actually survived in production. A roughly 25 per cent survival rate, and the tool was never the cause of death. Automations die because nobody inside the business understands or owns them. You have probably read that most corporate AI efforts fail, a stat that gets quoted endlessly (source: the MIT figure reported via forbes.com). The useful reading is the inverse. The ones that survive did not find a magic tool. They picked the right workflow and learned to own and debug it. As a builder on r/n8n put it, the real skill isn't building, it's diagnosing; anyone can wire up n8n or connect APIs, but the rare skill is listening to a store owner for 30 minutes and identifying the one workflow costing them the most. That is why owning it beats every tool debate. Self-hosted n8n takes the argument furthest, because there is no per-task meter, no overseas processor, and no vendor who can delete your setup. Australian owners already know what vendor lock-in feels like. On the accounting side, one wrote that after a software change everything had been permanently deleted with nothing they could do, on r/AusFinance, and another that you can no longer save a backup of your own company file because files are online only now, on r/ausbusiness. The lesson transfers straight to automation: if you do not own where it runs, you do not really own it.

Is n8n free? The self-hosted version is open-source and free to run, so your only cost is the server it runs on. n8n also sells a managed cloud plan priced by executions (source: n8n.io). Is Zapier or Make cheaper? It depends on your workflow shape. Zapier charges per task and Make per operation, so simple low-volume automations often suit Zapier, while complex multi-step scenarios can be cheaper on Make. High-volume workflows are frequently cheapest on self-hosted n8n, which has no per-run meter (source: zapier.com, make.com, n8n.io). Can these tools integrate with Xero and MYOB? Xero is widely supported across Zapier and Make. MYOB support is more variable. For any AU tool with a public API, self-hosted n8n can connect through generic HTTP requests even without a pre-built connector. Always check the current app directory before committing. Which is best for Australian data residency? Self-hosted n8n, run in an Australian cloud region or on your own hardware, keeps workflow data on infrastructure you control. Cloud Zapier and Make process data on their own, typically overseas, servers. Do I need a developer to self-host n8n? For a small setup, no, but you do need someone willing to run and maintain a server. If nobody on your team can or will do that, a cloud tool is the honest choice. What is the single biggest predictor of whether an automation survives? Ownership. An automation built and understood by someone who works in the business every day survives. One rented from an agency or bolted on by the busiest person in the company usually does not.