AUTOMATION TOOLS
Zapier Alternatives NZ (2026): Make and Custom AI Agents - Real Costs Compared
Three ways to get the same admin off your plate, what each one costs at the starter tiers in 2026, and where each one stops being the cheap option.
The short version. If your automations are simple and you run fewer than a few hundred a month, Zapier is fine and probably the cheapest thing you can do. If you have outgrown it on volume or on logic, Make does the same job with more room and a lower starter price. If the work needs judgement, touches sensitive data, or the subscription has grown past what a one-off build would cost, having a custom AI agent built for you is the third option. That last one is what we do, so read our part of this with that in mind.
Most New Zealand small businesses meet automation through Zapier. A form on the website creates a row in a spreadsheet, a new Xero invoice posts to a Slack channel, a Calendly booking sends a confirmation. It works, and then one day the invoice arrives and the owner asks whether there is a cheaper or better way.
This guide compares the three realistic answers for a small business here: stay on Zapier, move to Make, or have a custom workflow or AI agent built. It covers what each costs at the starter tiers in 2026, where the costs climb, and which situations suit which option. The prices are the vendors’ published figures as read in October 2026. They change, and they are in US dollars, so check the vendors’ pricing pages before you decide anything.
The three options in plain terms
Zapier
Zapier is the one most people start with. You pick a trigger, such as a new enquiry on your website, and add the steps that should follow. It connects to thousands of apps, including Xero, Google Workspace, HubSpot and most of the tools a New Zealand office already uses. Each time an action step runs, that is one task, and tasks are what you pay for.
Make
Make, which some people still know as Integromat, does the same job on a visual canvas. You draw the workflow as modules joined by lines, and it is easier to add branches, loops and error handling than it is in Zapier. Each time a module runs, that is one credit, and credits are what you pay for. The interface takes a little longer to learn, and the app list is smaller, though it covers the common tools.
A custom-built workflow or AI agent
The third option is to have someone build the automation for you in code, connected to the tools you already run. There is no per-task meter. The workflow does exactly what your process needs and can include an AI step that reads an email, extracts the details from a document or drafts a reply, with a person approving anything that goes out. The cost is up front, in build time, plus whatever it takes to keep it running. AUXA builds these, and our business process automation service page describes the work in more detail. Other developers and agencies in New Zealand offer the same thing.
What each one costs in 2026
These are starter prices. Both platforms step up in price as you use more tasks or credits, and both bill less per month if you pay for a year in advance.
| Option | Free tier | Starter paid plan | What you pay for |
|---|---|---|---|
| Zapier | 100 tasks a month, two-step Zaps only | Professional from US$19.99 a month billed annually (US$29.99 billed monthly); the task allowance depends on the plan size you pick | Tasks: one per action step that runs |
| Make | 1,000 credits a month | Core from $9 a month billed annually for 10,000 credits a month, with Pro from $16 and Teams from $29 | Credits: one per module that runs |
| Custom build (AUXA) | None, though the scoping conversation is free | One-workflow build from NZ$1,500 one-off; retainer from NZ$800 a month if you want it maintained | Build time, then maintenance; no per-run meter |
Prices change. Check the vendors. The Zapier and Make figures are from their published pricing pages, read in October 2026. Zapier’s page defaults to US dollars and has a currency selector that can show NZ dollars. Make’s page shows a plain dollar sign without naming the currency, and we read it as US dollars. Neither figure includes GST or whatever your card charges for a foreign-currency transaction. The AUXA prices are our own published pricing, in NZ dollars.
Two things make the platform prices harder to compare than they look. First, a task and a credit are not the same unit. A Zapier workflow with a trigger and three actions uses three tasks each run; the same workflow in Make might use four or five credits, because the trigger and any filter or formatting module count too. Second, the starter price buys the smallest plan. Zapier’s Professional plan is sized with a task slider and the price climbs as you move it, so a business running thousands of tasks a month pays well above the starter figure.
Three New Zealand examples
These are typical situations, not client stories. The numbers are illustrative, to show how the costs behave.
A plumber in Hamilton with a quote problem
Say a two-van plumbing business gets fifteen website enquiries a week and wants each one answered within a minute, with a reminder to the office if no quote has gone out in two days. That is two short workflows and maybe 300 tasks a month. Zapier’s starter plan covers it with room to spare, and the owner can build it on a Sunday afternoon. Make would do it for less, but the saving is a coffee a week and the learning curve is real. This is the case for staying on Zapier. Our page on automation for tradies and construction businesses covers what the next step looks like once quoting and scheduling join in.
An accounting practice chasing documents at year end
Now take a three-partner accounting practice with 400 clients. At year end it wants to send each client a checklist, chase the ones who have not replied at weekly intervals, log every reply against the client record and flag the stragglers to a partner. That is one workflow with branches, waits and a loop over hundreds of clients. In Zapier it is awkward to build and expensive to run, because every client and every chase is a task. Make handles the loops and branches naturally and its credits go further at this volume. This is the case for Make. The practice side of this, including what Xero already does on its own, is on our page on automation for accountants and bookkeeping firms.
A real estate office drowning in portal enquiries
Finally, a real estate office receiving enquiries from its website, Trade Me Property and realestate.co.nz, all in slightly different formats, some serious and some not. It wants each enquiry read, the buyer’s situation pulled out, a first reply drafted in the agent’s own voice and the hot ones pushed to the phone of whoever has that listing. Reading an unstructured email and deciding whether the buyer is serious is judgement, not routing. A platform can call an AI model to do it, but by then the workflow is a long chain of fragile steps and every enquiry burns several tasks or credits. A custom-built agent does the reading, the drafting and the handover in one place, with the agent approving each reply before it goes. This is the case for a custom build, and it is the kind of job described on our page on automation for real estate agencies.
Where Zapier stops being the cheap option
Zapier is cheapest when the workflows are short and the volume is low. Three things change that.
- Volume. Tasks are metered, so a workflow that loops over every client, every invoice or every job runs up the bill in proportion. The price per task falls at higher tiers, but the total still climbs.
- Logic. Paths, filters, delays and formatting steps are all available, but a workflow with many of them becomes hard to follow and each one is another step to pay for.
- Data. Everything that flows through a Zap passes through Zapier’s servers overseas. For most businesses that is fine. For a law firm, an immigration adviser or a health practice handling client files under the Privacy Act, it is at least worth a conversation.
Make answers the first two for a while, because credits are cheaper and branching is built in. It does not answer the third, because it is also a hosted platform running on overseas infrastructure. A custom build answers all three, at the cost of needing someone to build and look after it.
When a custom build is the wrong answer
We would rather say this plainly than have you find out after paying for it. A custom build is the wrong choice when the workflow is two or three steps, the volume is low, and you need it running this week. A platform will have it live in an hour for less than the cost of the scoping call. It is also the wrong choice if nobody in the business will own it afterwards. Code needs someone to answer when it breaks, which is what a retainer is for, and if you would rather not pay for that, a platform’s support desk is the better deal.
The honest test is simple. Add up what the platform would cost you over two years at the volume you expect, including the tier you will actually land on rather than the starter price. If that number is well under a one-off build, stay on the platform. If it is close to or above it, and the work is complicated or sensitive, get a quote for a build and compare.
How to decide, in four questions
- How many runs a month? Under a few hundred, Zapier or Make. In the thousands, price the tier you will really be on, and compare that with a build.
- Does any step need judgement? Reading an email, deciding what a document is about, writing a reply that sounds like you. If yes, you are in AI agent territory, and the question is whether a platform can host that agent cleanly or whether it should be built.
- Whose data passes through? Client files, medical details, immigration cases. If that data should not sit on an overseas platform, a build is the only one of the three that keeps it where you choose.
- Who will own it? A platform workflow can be owned by the office manager. A build needs a developer on call, in-house or on a retainer.
If you want a second opinion on your own answers, that conversation with us is free and we will say so if a platform is the better fit. Our build process explains what happens if you go ahead.
Frequently asked questions
Is Make cheaper than Zapier for a small New Zealand business?
At the starter tiers, usually yes on the sticker price: Make’s Core plan lists at a lower monthly figure than Zapier’s Professional plan and includes more allowance. But the two meter differently. Zapier counts a task each time an action step runs; Make counts a credit each time a module runs, and one workflow can use several modules. Price the workflow you actually plan to run, not the headline.
Do I pay GST or get charged in NZ dollars?
Both vendors publish their prices in US dollars by default, so the NZ dollar amount on your card statement moves with the exchange rate. Whether GST is added depends on the vendor and on whether you have given them a GST number as a registered business. Check the invoice for the first month before you budget the year.
Can I move my Zaps to Make without starting again?
Not by import. Zapier workflows do not export in a form Make reads, so a move is a rebuild. For a handful of simple Zaps that is an afternoon. For a tangle of twenty with filters and paths, write them down first and rebuild only the ones still earning their keep.
When does a custom-built AI agent make more sense than either platform?
When the work needs judgement rather than routing, when the data must stay out of a third-party platform, or when volume has pushed the subscription past what a one-off build would cost. A custom build is a bad choice for a two-step workflow you need running this week.
What does a custom automation build cost in New Zealand?
AUXA’s published prices are a focused one-workflow build from NZ$1,500, scoped and quoted before work begins, and a monthly retainer for ongoing development, monitoring and support from NZ$800. Any platform or AI subscriptions the workflow uses are billed to you directly. Other developers price differently, so compare like with like.
Can I keep Zapier for some things and build the rest?
Yes, and that is often the sensible answer. Leave the simple, low-volume Zaps where they are, and build only the one workflow that is complicated, high-volume or sensitive. A custom workflow can trigger a Zap and a Zap can call a custom workflow, so the two can share the work.
Sources
AUXA is based in Auckland and builds custom automation and AI agents for New Zealand and Australian service businesses. If you are weighing a Zapier alternative and want to know what a build would cost for your workflow, tell us what the workflow is and we will give you a straight answer.