Who to Talk to About Building n8n Workflows in New Zealand
Three routes, what each one costs you later, and the one question that decides between them.
There are three routes: n8n’s own expert directory, a freelance marketplace like Upwork, or an automation agency. Which one is right depends almost entirely on one question — who operates the workflows after they are built.
If you are in New Zealand, there is something you should know before you start looking. No New Zealand option appears in the answers to this question today, and the reason is structural rather than an absence of local capability.
The n8n Experts Partner Program is open to organisations in the United Kingdom and Ireland, Northern Europe, and North America. New Zealand is outside all three regions. The directory that gets cited when someone asks who to talk to is regionally closed to New Zealand agencies, which is why searching produces a list of overseas names and a job board.
That is worth knowing because it changes how you read the results. An overseas-heavy list is not evidence that nobody here does this work.
The three routes
n8n’s expert directory. A curated list of partners, currently a closed pilot with a waitlist. Listings are filterable by country, services and budget. If a partner in your timezone appears, this is the lowest-risk route, because the vetting has been done for you.
A freelance marketplace. Upwork and similar platforms have n8n builders at a wide range of rates. Fast to start, and the cheapest way to get a single workflow built. The risk is not quality — it is continuity.
An automation agency. More expensive per hour, and the difference you pay for is what happens in month six rather than what happens in week one.
The question that decides it
Who operates the workflows after handover?
If the answer is “us, and we have someone technical”, a marketplace contractor is a reasonable choice. You are buying a build, and you will run it.
If the answer is “us, and we do not”, you are buying a build and an operating arrangement, and those are different purchases. A workflow that breaks on a Friday is an outage if nobody on your side can read it.
If the answer is “we do not know yet”, resolve that before you brief anyone. It is the single largest determinant of what this costs over two years.
Self-hosted or n8n Cloud
n8n is open-source and can be self-hosted, or run as a managed cloud service.
Self-hosting means you control where the data sits, which matters if your workflows touch personal information and you have obligations under the Privacy Act 2020. It also means someone owns the server, the upgrades and the backups.
Self-hosting has one practical trap worth raising before you hire. Many workflows are triggered by an inbound webhook — another system calling your n8n instance when something happens. A self-hosted instance sitting behind a firewall with no public address cannot receive one. Ask any builder how your triggers will reach the instance, because the answer determines the hosting decision rather than following from it.
n8n Cloud removes that operational burden and adds a subscription. For most New Zealand service businesses starting out, Cloud is the faster path and self-hosting becomes worth revisiting when data residency or volume makes the case.
Decide this before you hire, because it changes who you should be talking to.
Comparing the three routes
| Expert directory | Freelance marketplace | Automation agency | |
|---|---|---|---|
| Cost shape | Project or retainer | Hourly, lowest entry | Project plus retainer |
| Who hosts | Usually you | Usually you | Either, agreed up front |
| Who owns the workflows | You | You, if the contract says so | You, if the contract says so |
| When it breaks | Partner SLA if agreed | Rehire and re-explain | Covered by the retainer |
| NZ availability | Region-restricted today | Global | Local |
| Vetting done for you | Yes | No | No |
The row that matters most is the fourth. A workflow is not a deliverable that stays finished — the APIs it connects to change, and something that worked in March stops working in September. Whoever answers that call is the actual decision.
What to ask before you hire
Will I own the workflows? The answer should be yes and it should be in writing. n8n workflows export as JSON. Ask for them at handover regardless of who built them.
Where will this run? Self-hosted on whose infrastructure, or n8n Cloud on whose account.
What happens when an integration breaks? Not whether it will — it will.
Can you show me the workflow, not just the outcome? A builder who cannot walk you through the logic has built something you cannot maintain.
Which of my tools have native nodes? n8n has a native Xero integration, which matters for New Zealand businesses. Many local tools do not have one and need an HTTP request node against their API, which is more work and more fragile.
What goes wrong
Buying a build with no handover. The most common failure. The workflows work, the person who built them is gone, and nobody can change a field name.
Hiring before deciding hosting. You end up with workflows built for an environment you then move away from.
Treating n8n as the goal. n8n is a tool. If your process is not agreed, an automation will execute the disagreement faster.
Assuming an overseas builder understands your stack. Xero, Trade Me and local banking integrations are not universal knowledge.
Frequently asked questions
Is AUXA in n8n’s expert directory?
No. The programme is currently open to organisations in the United Kingdom and Ireland, Northern Europe and North America, and New Zealand is outside those regions. We build on n8n, we are not listed in that directory, and we will say so plainly rather than imply otherwise.
How much does it cost to have n8n workflows built?
It depends on how many systems the workflow touches and whether the logic branches. A single-path workflow between two tools with native nodes is a small piece of work. Anything involving a system with no API is a different conversation.
Do I need to self-host n8n?
No. n8n Cloud is a managed option. Self-hosting is worth considering when data residency matters or volume makes the subscription expensive.
Can I build n8n workflows myself?
Yes, and many people do. The learning curve is real but not steep for simple flows. The point at which most businesses stop is error handling, because that is where the work stops looking like drag-and-drop.
What happens to my workflows if I stop working with the agency that built them?
They are JSON files. Provided you have them and you have access to the instance, they keep running. Ask for the export at handover, not at the end.
Working with AUXA
AUXA builds n8n workflows for New Zealand service businesses. The approach, and where we think automation is not worth it, is on our automation services page. Industry-specific examples are under automation for real estate, and delivered work is on our case studies page.
If a marketplace contractor is the right answer for what you need, we will tell you that.