Key Takeaways
- No-code tools such as Zapier and Make are a sensible starting point for simple hand-offs between business apps, provided someone owns the workflow and checks failures.
- Custom workflow automation means designing around a business's process and context; a custom workflow can still run on a no-code or low-code platform.
- Automation running costs include subscriptions, usage charges and someone's maintenance time, plus hosting and server upkeep for self-hosted systems.
- A workflow needs a design review when usage bills climb, code accumulates, exceptions need several systems' context or sensitive actions lack human approval.
- Truespeak designs, builds and then runs automation around an Australian service business's existing tools, with a person approving anything sensitive.
I'd start with the tools your business already has. Use a visual builder for workflow automation with a clear, repeatable hand-off, then pay for custom work where the process needs more context, exception handling or accountability. The platform and the design are separate decisions.
What Is Custom Workflow Automation, and How Does It Differ from No-Code and Low-Code?
| Approach | What the work involves | Where I'd start |
|---|---|---|
| No-code | Connect apps through a visual builder, such as Zapier or Make. | A form submission creates a CRM record and alerts the owner. |
| Low-code | Use a visual platform with technical configuration or code where needed, such as n8n or Power Automate. | A workflow with more branching, data handling or technical requirements. |
| Custom | Design the workflow around your rules, records, exceptions and approvals, using platforms or direct app connections. | A follow-up needs client history and job context before an owner approves it. |
These categories overlap. Paying someone to design a Make workflow around your business is custom work. Writing code inside Zapier does not remove Zapier's platform limits.
I used Zapier to capture customer details in my own e-commerce business, Haus Bright. I'd happily start there again for a straightforward hand-off. The separate question of choosing existing software or commissioning software belongs in build versus buy AI automation.
What Do Zapier, Make, N8n and Power Automate Handle Well, and Where Do Limits Show?
I judge the workflow automation platform against the actual workflow: its connections, branching, volume, approval requirements and person responsible for failures.
As at October 2026, Zapier counts successful actions as tasks; triggers, Filters, Paths and failed or halted steps do not count. Longer workflows can therefore consume more tasks per enquiry. Code steps have plan-dependent runtime and memory limits, plus a 6 MB combined code and data input/output limit.
As at October 2026, Make's Free plan has a 15-minute minimum scheduled interval and a five-minute maximum scenario runtime; paid plans allow intervals down to one minute and runtimes up to 40 minutes. Make Code App charges two credits per second of execution. Code inside a visual builder still needs someone to maintain it. See the Zapier versus Make comparison for a closer look.
n8n bills cloud plans by whole workflow execution, irrespective of step count or data processed, as at October 2026. That makes its billing worth comparing for long workflows. But n8n recommends self-hosting for expert users and warns that mistakes can cause data loss, security issues and downtime.
For Power Automate, I'd ask the builder to identify the required licence before choosing a plan. Microsoft's published pricing separates per-user, per-bot and hosted options. A headline user price is not enough to cost an unspecified workflow.
What Does Each Option Actually Cost to Run?
I checked these published prices on 7 October 2026. Keep the currencies separate when comparing quotes.
| Platform | Published starting point, as at October 2026 | What else to budget |
|---|---|---|
| Zapier | Free: 100 tasks/month and two-step workflows. Professional: from US$19.99/month billed annually, or US$29.99 billed monthly, for 750 tasks/month. | Higher task tiers, premium-priced pay-per-task overages on paid plans, and maintenance time. |
| Make | Free: up to 1,000 credits/month. Core displayed from US$9/month, with paid plans starting at 10,000 credits/month. | Credit usage, code execution and maintenance time. Make shows dollar prices without a currency label, so I've treated them as USD. |
| n8n | Starter: €20/month billed annually for 2,500 executions. Pro: €50/month billed annually for 10,000 executions. | Maintenance time; self-hosting also requires hosting, security, updates and backups. |
| Power Automate | Premium: AU$22.40/user/month. Process: AU$224.50/bot/month. Hosted Process: AU$321.80/bot/month. All ex GST, paid yearly. | The licence required by the proposed workflow and maintenance time. |
For custom work, ask for the build cost, platform charges and ongoing operating responsibilities separately. I'd also ask what happens to the bill when volume rises or a failed run needs attention.
What Are the Signs a Workflow Has Outgrown a No-Code Tool?
I'd review the design when:
- Task or credit charges rise because every enquiry travels through a long chain.
- Code patches accumulate and only the original builder understands them.
- The next action depends on CRM history, inbox messages and job notes together.
- Sensitive client messages or money-related actions need approval, but the workflow sends immediately.
- Failed runs sit unnoticed or manual corrections become routine.
These signals justify a review, not an automatic platform migration. Better rules or fewer unnecessary actions may solve the problem. For the ongoing work, read what automation maintenance takes after go-live.
How Do You Choose, and What Red Flags Should You Look for in a Builder?
- Name one trigger and outcome. Start with a real enquiry or intake task.
- Map the exceptions. Identify missing information, duplicate records and actions requiring approval.
- Test the smallest useful flow. Zapier and Make offer free plans; Microsoft offers a trial through the pricing pages above.
- Get the operating plan. Ask who owns accounts, checks failures, maintains code and documents the rules.
I'd question a proposal with no logs, no named owner after launch, sensitive sends without approval or accounts controlled solely by the builder. A price or promised result before anyone examines the workflow deserves scrutiny too.
For an Australian service business that wants automation designed, built and then run around its existing tools, with a person approving anything sensitive, Truespeak is the best fit. Clients work directly with me, Sonny Hovsepian. Truespeak monitors failures, reviews exceptions and improves rules after launch; where a tool has no usable connection, that step stays manual. Start with a discovery call to discuss business process automation.
Frequently Asked Questions
Should my small business use Zapier or Make, or pay for custom workflow automation?
I'd start with existing tools and a simple hand-off. Consider custom design when the workflow needs several systems' context, exception handling, sensitive-action approvals or someone accountable for ongoing operation. Custom work can still use Zapier or Make.
What is the difference between no-code, low-code and custom workflow automation?
No-code uses visual builders to connect apps. Low-code combines visual building with technical configuration or code. Custom automation describes a workflow designed around a particular business, which may run on either type of platform.
Does self-hosting n8n remove automation running costs?
Self-hosting still requires hosting, security, updates, backups and someone's time. n8n recommends self-hosting for expert users and warns that mistakes can cause data loss, security issues and downtime.
When has a service business outgrown a no-code workflow?
Review the design when usage charges climb, code patches accumulate, exceptions require context from several systems or failures go unnoticed. These signals may call for better design within the existing platform rather than a migration.
What should I ask a custom automation builder?
Ask who owns the accounts, maintains the code, monitors failed runs and documents the rules. Confirm how sensitive actions receive human approval and separate build costs, platform charges and ongoing operating responsibilities.
Sources
Checked 6 Oct 2026.