The one you can run on your own server. Read the licence before you resell it.

What the n8n API does and does not allow

The self-hostable automation platform. The reason a workflow can run on a server you control, in a country you choose.

Everything in the strip above is n8n’s own published documentation, fetched 1 September 2026 and linked to the page it came from. We have not paraphrased it into something friendlier, because the exact wording is what you need when a limit bites at four in the afternoon.

What follows is what those facts mean for a build — the constraints that change a design decision rather than the ones that are merely true. If you want the same treatment for the other eight systems side by side, that is the capability register. If you want to know whether we have built against both sides of a particular pairing, the integration checker answers that specific question.

Executions, concurrency, and which one actually limits you

An n8n execution is one run of an entire workflow, regardless of how many steps it has or how much data it moves. That is a fundamentally different meter from Zapier, where every successful action costs a task — and it is why the two platforms cannot be compared on price without knowing the shape of your workflows.

A workflow with twenty steps that runs five hundred times a month is 500 executions on n8n and up to 10,000 tasks on Zapier. That gap is the whole argument for n8n on complex work, and it is real.

But the monthly execution count is rarely the binding constraint. Concurrency is: five simultaneous production executions on Starter, twenty on Pro, two hundred or more on Enterprise. A workflow that takes thirty seconds and gets triggered ten times at once queues most of them, in order, until capacity frees. The plan you need is set by your busiest minute rather than your monthly total, and that is the sum most people do not do.

• Size on the burst Peak simultaneous triggers times average run duration. That number picks the plan; the monthly execution count almost never does.
• Queued is not failed Executions beyond the limit wait in order rather than erroring. Good behaviour, and it still means a customer waiting.
• Only production runs count Manual runs, sub-workflow runs and error executions sit outside the concurrency limit. Useful while you are building.

Australian data residency, and the licence clause underneath it

n8n Cloud runs on Microsoft Azure in the European Union, with more locations stated as coming. There is no Australian region today. What n8n has that nothing else in this register has is a self-hosted option — and a self-hosted instance sits wherever you put the server, which can be Sydney or Brisbane.

For a business handling health, disability or government-adjacent information, that is the difference between a workable answer and no answer at all. Every other automation platform here is United States-hosted with no regional option.

The clause to read before building a business on it is the Sustainable Use License. It grants free use, modification and redistribution, limited to your own internal business purposes or non-commercial use — and it explicitly prohibits "hosting n8n and charging people money to access it" and white-labelling it for customers. Consulting on n8n and supporting it are explicitly permitted. Running a hosted instance and billing clients for access to it is not. That is the constraint agencies discover latest and most expensively.

Rate limits and what breaks at scale

n8n publishes no rate limit for its own API, which is unusual and, in context, reasonable — on a self-hosted instance the limit is your server. What it publishes instead is the concurrency model above, plus cursor pagination at 100 records by default and 250 maximum.

On n8n Cloud two hard numbers do bite. Webhooks time out at 100 seconds behind Cloudflare, returning a 524 — so anything slower has to acknowledge immediately and do the work asynchronously. And webhook payloads cap at 16MB, raisable only on a self-hosted instance through an environment variable.

One more that catches growing teams: only one webhook can be registered per path and HTTP method across the whole instance. Two workflows cannot both listen on POST /invoice. Obvious once you know it, and it surfaces exactly when a second person starts building workflows.

What n8n does not publish

4 of the thirteen fields we track are simply absent from n8n’s documentation: token lifetimes, what happens when a webhook delivery fails, any bulk or batch limit and what the test environment gives you.

This is the part of an integration page that competitors leave out, and it is the part that costs money. An undocumented rate limit is not an academic gap — it means the first time you find the ceiling is in production, on someone else’s business, usually on the busiest day of their month.

We are not going to fill these in with figures from a forum thread. Numbers circulate for most of them, and some are probably right, but we cannot show you where they came from and neither can the person who posted them. When we have measured n8n properly under load, those figures will appear here with the date we measured them and the conditions we measured them under. Not before.

What we have built, and what we have not measured

We have implemented against n8n in production. That is a real fact and it is also a limited one — it tells you we have solved this system's problems before, and it does not tell you how fast, how reliably, or at what volume.

The honest position is this. Everything on this page above the line is the vendor's published documentation, which we fetched, dated and linked rather than paraphrased. Nothing on this page is a Kindra measurement, because our measured register is not finished and publishing half of it dressed up as all of it would make this page less useful, not more.

What we would do on an engagement is measure the specific things that matter for your build — the endpoints you depend on, at your volume, with your data — and hand you those numbers whether or not they suit us. If they say the integration is harder than we quoted, you get told that too. Start with a Leak Check, or read how we work first if you would rather know the shape of it before talking to anyone.