PILLAR · Checklist

Production-Ready n8n Checklist: 5 Rules Every Self-Hoster Skips

2026-10-20 · William Ayad · 7 min read

Why checklists beat memory at 2 a.m.

Pilots with ten thousand flight hours still read a printed checklist before takeoff — not because they forgot how to fly, but because memory is exactly the thing that fails when you are tired, rushed, or fixing something small. Self-hosted n8n production failures share that shape: they are rarely caused by what you never learned, and almost always caused by the one step you were certain you did. These five rules are the items on that checklist, each verifiable in about sixty seconds.

Rule 1 — Never deploy an un-audited export

The exported workflow JSON is the only artifact that travels from your editor to production. Scanning it before deploy is the single highest-leverage habit in self-hosted n8n: localhost URLs, broken node references, embedded secrets — all visible in the file, all invisible in the editor. The silent-failure debugging map names the five killers this rule hunts. If auditing sounds heavy, know that the whole check takes under a minute with a browser-only tool — and skip it for one deploy and you have not saved a minute, you have bought a lottery ticket.

Rule 2 — Treat every webhook as a public door until it is not

If your workflow has a Webhook node without an auth header, signature check, or HMAC secret, anyone with the URL can run it. In production that is not a theoretical risk — endpoint scanners find things by construction, not by luck. The rule: no workflow ships with an unauthenticated inbound webhook unless the payload is provably harmless. One eyeball pass on your trigger nodes, sixty seconds, done.

Rule 3 — Retries are the difference between noise and loss

External APIs throttle. DNS hiccups. Containers restart mid-request. These are normal Tuesday events in production — and without Retry On Fail configured per node, each one silently deletes a client deliverable. Configure max tries and a wait interval on every network-facing node (HTTP Request, most CRM and payment nodes), and transient failures evaporate. Skip this rule and you are one rate limit away from explaining a missing invoice run to a client.

Rule 4 — Separate secrets from structure

Credentials belong in n8n's credential store, never in node parameters, webhook bodies, or code nodes. The exported JSON should carry structural references, not usable keys — because that file will travel: to Git, to a client handoff, to a support paste. If your exports contain live tokens, your backup and recovery story inherits the leak too, which is a more expensive conversation than rotating one key.

Rule 5 — Monitor runs, validate exports

Production observing is a second, separate habit from pre-flight checking. You need an execution failure to arrive as a notification, not as an angry client message three days later — see the monitoring layer piece for the deceptively simple pattern. Combined, rules 1 and 5 form the complete defense: one kills failures before birth, the other catches the rare one that slips through.

The whole checklist in sixty seconds

Export the workflow, open the free n8n workflow audit, paste, read five plain-language verdicts. The checker runs entirely in your browser tab — nothing uploads, nothing is stored, no account required. The rules above are exactly the checks it performs deterministically, every time, without fatigue.

Where the free audit stops (honesty first)

The free page enforces these five rules with perfect consistency. It deliberately does not cover the full 24 production rules, the 21 documented failure fixes, the 24-point preflight checklist, or the client-branded PDF report. Those live in the full n8n Reliability Kit — one-time $39 (disclosing: it is mine), no subscription, no seat limits, everything still local in your browser. Buy it the day the free checks flag something you did not expect — the deeper layers will pay for themselves that same afternoon.

Checklists are not for the forgetful. They are for the professional who knows exactly how expensive a forgotten sixty seconds costs at 2 a.m.