n8n, Zapier or Make: choosing an automation tool

A lot of small-organisation admin is copying things from one place to another. A website enquiry gets retyped into a spreadsheet. A new member gets added to the mailing list by hand. A booking confirmation is written out fresh each time. Automation tools take those jobs off your plate by connecting your website, forms, email and other software so that one action triggers the next.

Three tools come up most often: Zapier, Make and n8n. All three are capable. The differences that matter most for a small team aren’t the feature lists. They’re about hosting, data and who keeps things running.

The short version

• Zapier is the easiest to start with and connects to a very wide range of apps. It’s a hosted service, so there’s nothing to install or maintain.
• Make is also hosted, with a visual canvas that suits workflows with branches, filters and several steps. It’s a good middle ground once a workflow outgrows simple “when this, do that”.
• n8n can be used as a hosted service or installed on your own server. Self-hosting gives you the most control over your data, but someone has to look after it.

Hosted or self-hosted

With a hosted tool, the company runs the servers, applies the updates and keeps the lights on. You pay a subscription and log in. For most small organisations without technical staff, this is the sensible default.

With a self-hosted tool, the software runs on a server you control. n8n is the main option of the three here. Its source code is publicly available under what it calls a fair-code licence, and you can run it yourself for your own organisation’s use. That can mean lower running costs for busy workflows and full control over where data lives. It also means updates, backups, security and monitoring become your responsibility, or your provider’s.

Self-hosting is not free just because the software is. Someone’s time goes into it every month. If no one is going to own that, choose a hosted service.

Where your data goes

Automations often carry personal information: names, emails, phone numbers, sometimes enquiry details that people shared in confidence. Every tool in the chain sees that data on its way through.

Zapier says it hosts customer data on servers in the United States. Make lets you choose a data region when you set up an account. With self-hosted n8n, the data stays wherever you put the server, which can be in Australia.

For many workflows, overseas hosting is perfectly acceptable, as long as your privacy policy says so honestly. But the Australian Privacy Principles include rules about sending personal information overseas, and organisations in health, community services, education or anything involving children should think carefully. A good habit is to pass only the fields a workflow actually needs, rather than the whole form submission.

Cost and how it grows

All three have free or low-cost ways to start, and all three charge more as you use them more. Zapier and Make price by how much activity your workflows generate, so a workflow with many steps that runs often costs more than a simple one. n8n’s hosted plans count whole workflow runs rather than each step inside them, and self-hosting swaps a subscription for server and maintenance costs.

Before choosing, list the workflows you actually want, roughly how often each would run and how many steps it has. Then compare current pricing on each tool’s own site, because plans change often.

Who maintains it

Automations break quietly. An app changes its login, a form gets a new field, a password expires, and the workflow stops without telling anyone. Weeks later someone asks why no enquiries have come in.

Whichever tool you choose:

• Name one person who owns each workflow and knows what it’s meant to do
• Turn on error notifications and send them to an inbox someone reads
• Keep a short plain-language note of what each workflow does and which accounts it uses
• Review your workflows a couple of times a year and switch off any you no longer need

If you’re adding AI steps, such as summarising enquiries before they reach your inbox, the same care applies as anywhere else. We covered that in adding AI to your website responsibly.

Our rule of thumb

If nobody on your team wants to look after a server, choose Zapier or Make and keep the data you send through them to a minimum. If you have, or can arrange, ongoing technical care and need control over where data lives, self-hosted n8n is well worth considering. Either way, start with one workflow that saves real time and build from there.

Where to start

Pick the most repetitive task in your week, write down each step, and ask whether a tool could do it reliably. If it could, try it on a free plan first. Keep it small, check it works for a few weeks, then decide whether it’s worth paying for.

If you’d like help choosing or setting up automations that fit how your team works, see our automation service, or tell us what you’re working on. We’ll tell you honestly when a spreadsheet and a good habit will do the job instead.