Zapier and Make have made automation available to almost every business. You can connect a form to a CRM, a CRM to an email tool and a spreadsheet to almost anything, often in an afternoon and without a developer. For a lot of workflows, that's exactly the right answer.
But some automations grow. A simple zap picks up conditions, lookups and workarounds. Volumes climb. A failure goes unnoticed for a week. At some point the question becomes whether no-code is still the right tool, or whether the workflow needs a custom integration.
This article gives a fair answer to that question, including when to stay exactly where you are.
The short answer
Use Zapier, Make or Power Automate when the workflow is simple, the volume is moderate, both systems are supported and a failure is easy to spot and fix. Consider a custom integration when the workflow carries business-critical data, needs validation and two-way sync, has lots of exceptions, or runs at a volume where usage-based costs and failures become hard to manage.
Many businesses end up with both: no-code for the simple, low-risk automations and a custom integration for the one or two workflows the business depends on.
What no-code tools do well
No-code automation platforms are genuinely useful, and we recommend them regularly. They're strong when:
- The trigger and actions are clear. "When a form is submitted, create a contact and notify the team" is a perfect fit.
- The apps are supported. Both systems have well-maintained connectors on the platform.
- You want to move quickly. You can test an idea before deciding whether it's worth investing in.
- The stakes are low. If a run fails, someone can redo it by hand without much harm.
They also include more resilience than people often realise. For example, Zapier's replay feature can automatically retry failed runs on eligible plans, and Make has built-in error handling that lets you define what happens when a step fails.
How the costs scale
Pricing on these platforms is tied to usage, so it's worth understanding how usage is counted rather than comparing headline plan prices.
- Zapier measures usage in tasks. According to Zapier's help centre, a task is a successful action step. Triggers, filters and paths don't count, and failed steps don't either. A zap with two actions that runs ten times uses twenty tasks. Plans include a task allowance, and Zapier can switch to pay-per-task billing if you go over.
- Make bills scenario activity in credits, which generally line up with the operations a scenario performs.
- Power Automate is included with many Microsoft 365 licences for flows that use standard connectors. According to Microsoft's licensing FAQ, premium and custom connectors need a separate premium licence.
The practical point is that cost grows with the number of runs and steps. A workflow that loops over line items, searches for records before updating them or runs every few minutes can use far more than you'd expect. That isn't a reason to avoid the platforms. It's a reason to check the numbers as volumes grow.
Signs you're outgrowing no-code
Failures are quiet and expensive
If a failed run means a customer isn't invoiced, an order isn't dispatched or a candidate's details go missing, you need more than an email notification. You need to know what failed, why, what data was affected and how to fix it safely, ideally without creating duplicates when you rerun it.
You need to check data, not just move it
Most no-code flows move whatever they receive. Business-critical workflows often need validation first: is the ABN present, does the job reference exist, does the total match, is this a duplicate? Building that logic in a visual tool is possible, but it gets hard to read and harder to maintain.
You need a real two-way sync
Keeping two systems in step, where either side can change a record, is one of the hardest integration problems. You need rules for which system wins, how to avoid loops and what happens when both change at once. That's where purpose-built logic usually beats a pair of opposing zaps.
Nobody fully understands the automations anymore
Twenty zaps built by three people over two years, with no documentation, is a common situation. When something breaks, nobody's sure which automation caused it.
You need an audit trail
Some workflows need a reliable record of what happened to each item: when it arrived, what was changed and who approved it. Platform run histories help, but they may not be kept for as long as you need or in the form your team or auditors expect.
What a custom integration gives you
A custom integration is code written to connect your systems the way your business works. Done well, it gives you:
- Validation and business rules applied before data moves.
- Clear handling of retries, duplicates and partial failures.
- Logging that shows what happened to each record.
- Alerts that go to a named owner with enough detail to act.
- A clear source of truth for two-way sync.
- Code and credentials your business owns.
The trade-offs are real too. A custom integration takes longer to build than a zap, costs more up front and needs maintenance, because the systems on either side keep changing.
Our work for Huntress Recruitment is a good example of where custom work made sense. Vacancy information had to move consistently between Bullhorn, SEEK and the company's WordPress website, with public-facing job details held separately from the internal Bullhorn record. That kind of structured, multi-channel workflow, with rules about which fields go where, is where custom work tends to fit.
The hybrid option
You rarely have to choose one approach for everything. A sensible setup for many businesses is:
- Keep no-code automations for notifications, simple handoffs and experiments.
- Move the one or two workflows that carry money, customers or compliance into a custom integration.
- Document everything, including which automations exist, who owns them and what happens when they fail.
This keeps the speed of no-code where it's useful, without betting core operations on it.
When a custom integration isn't the answer
Don't replace something that works. If your automation is simple, failures are rare and easy to fix, and the platform cost is reasonable for the value, stay where you are. A custom build also isn't the fix if the underlying process is unclear. If the team can't agree on the rules, writing them in code just makes them harder to change.
And sometimes the right move is a native integration you haven't switched on yet. Our guide to what to do when your business software doesn't integrate covers that option and the others, in the order we usually check them. If you're still working out where the gaps are, the hidden cost of tools that don't talk to each other is a good place to start.
Frequently asked questions
Is Zapier or Make better?
It depends on the apps you use, how complex the workflow is and how your team prefers to work. Both are capable. Choose the one with well-maintained connectors for your systems and a pricing model that suits your volumes.
Can you fix our existing zaps instead of replacing them?
Often, yes. Sometimes the right answer is to tidy up, document and add proper error alerts, rather than rebuild. We'd look at what you have before suggesting anything new.
Will a custom integration break less?
It can fail less silently, because you can design the logging, validation and alerts around your workflow. But any integration can break when a connected system changes, so it still needs monitoring and maintenance.
Who owns a custom integration?
You should. Make sure you have access to the code, the hosting and the credentials, and that it runs under business-owned accounts rather than someone's personal login.
What does a custom integration cost?
Custom software and automation projects typically start from A$2,500. Final pricing depends on the systems involved, complexity and scope. For a larger or more complex integration, we'd recommend an initial consultation so we can look at both systems first.
Get a second opinion on your automations
If you're running no-code automations that have become fragile, expensive or hard to follow, we're happy to take a look. Sometimes the answer is to tidy up what you have. Sometimes it's to move one workflow to a custom integration. Either way, you'll get a straight answer.
Get in touch and tell us which automation worries you most.