Setting up n8n has two decisions and four steps. First decide cloud vs self-hosted: n8n Cloud (about A$35–40/month) for zero ops, or self-hosted (A$5–50/month on a VPS) for data control and lower cost at volume. Then: deploy n8n with Postgres behind a reverse proxy, lock the editor behind auth and an IP allow-list, connect your apps with credentials, and build one workflow end-to-end before scaling. Most businesses are running their first useful automation within a day or two.
The four-step setup
- Deploy. n8n Cloud (sign up and go) or self-hosted with Docker Compose + Postgres + a reverse proxy. See self-hosting n8n in Australia for the onshore version.
- Secure. Put the editor behind authentication and an IP allow-list or VPN; disable public sign-up; keep secrets in env vars.
- Connect. Add credentials for the apps you use (Xero, HubSpot, Slack, Gmail) once, then reuse them across workflows.
- Build one workflow. Pick a single high-volume task and ship it end-to-end with logging and error handling before adding more.
If you want it audit-grade and shipped in ~2 weeks, that is the Spark plan (from A$2,400) — and you own the code.
Related questions
Do I need to know how to code to use n8n?
No for most workflows — n8n is a visual node editor. You only reach for the JavaScript or Python code node for edge cases like custom transforms. That said, a production-grade build (error handling, logging, retries) benefits from someone who has shipped n8n before.
Cloud or self-hosted for a first n8n setup?
Start on cloud if you just want to try it and have no data-residency needs. Self-host from the outset if you have onshore data requirements or expect real volume, because the cost is flat rather than per-execution. You can migrate between them since workflows are portable JSON.
Still need a hand?
Book a 15-minute map (US$50, credited to a build) and we will scope it with you — or send a note and we will add the answer here.