n8n Workflow Automation

The billing, mostly. Zapier charges per task, so a workflow with twelve steps costs four times one with three, and the price grows every time the volume does. n8n charges for the run and ignores what happens inside it. The other difference is the ceiling: every n8n node opens into code, so a process doesn’t have to stay inside what the visual builder can express. For a few hundred runs a month, Zapier is simpler and we’ll say so.

No. We scope it, build it, and run it, and most clients never open the editor. Teams that want in get full access and a walkthrough of how their workflows are put together, because the visual builder is genuinely readable once someone shows you the shape of it. Either way the workflows are yours, exported and in your accounts, not locked inside ours.

Almost certainly. n8n runs queue mode for high throughput, and the jobs that break it are well past where most Australian businesses operate. The more common limit isn’t n8n at all, it’s the API on the other end, and rate limits get designed around with batching and retries rather than wished away.

Around 400 tools have a native node, including HubSpot, Xero, Salesforce and Slack. Google Workspace, Notion, Airtable and the usual databases are covered too. Anything without one gets connected through its API with an HTTP node, which in practice means if a system has a documented API, it can be wired in. We check this during scoping, before anyone commits to a build.

Yes, and sometimes it’s the reason to pick n8n at all. Health, legal and government work often can’t send client data through someone else’s cloud, and self-hosting puts the whole platform on infrastructure the business controls. The trade is that a server needs maintaining, so we host on n8n Cloud unless there’s a real reason not to.

Most land between $3,000 and $15,000, quoted fixed before anything starts. A two-system sync sits near the bottom; a multi-step pipeline with AI processing, branching and error handling sits near the top. Running costs afterwards are hosting and model tokens, which for most teams is tens of dollars a month rather than hundreds.

It tells someone. Every build ships with error handling on the steps that can fail and an alert to Slack or email when one does, plus a log of every run showing what came in and where it stopped. Workflows break because the tools around them change, an API version moves or a field gets renamed, and the small retainer clients take covers fixing that.