Studio
Black Friday

Up to 70% off kits30% off services

Ends in
All Tools
n8n · Free Check

n8n Production Readiness Check

Fifteen yes-or-no questions about the n8n your business depends on: error alerts, hosting and backups, credentials and access, workflow design, and who owns it all. Five minutes, a score, and a fix for every gap. Works for n8n Cloud and self-hosted. Answers stay in your browser.

1.Errors & alerts

  1. Every production workflow has an error workflow that alerts a person in Slack, Teams or email.
  2. Workflows that should always change something fail loudly when a run does nothing.
  3. Something outside the n8n server checks that n8n is up and its webhooks respond.

2.Hosting & backups

  1. The n8n database is backed up at least daily, and someone has restored a backup to prove it works.
  2. n8n's encryption key is stored safely somewhere other than the server itself.
  3. Self-hosted production n8n runs on PostgreSQL rather than the default SQLite file.
  4. You know which n8n version you run, and updates happen on a schedule after someone reads the release notes.

3.Credentials & access

  1. Credentials use service accounts or API keys owned by the company, not someone's personal login.
  2. Public webhooks check a secret, header or signature before acting on a request.
  3. Only a few named people can edit production workflows, and the owner account uses two-factor authentication.

4.Workflow design

  1. A workflow that runs twice for the same order, invoice or contact will not create a duplicate.
  2. Steps that call outside APIs retry on temporary errors and respect rate limits.
  3. Changes are tested with test data or a dry-run switch before anyone edits a live workflow.

5.Ownership & cost

  1. You have a list of every active workflow with what it does and who owns it.
  2. You know your monthly executions, and they fit your plan or server with room to grow.

Want someone to check the real instance?30% OFF

Our $349$499 n8n Workflow Audit reviews every active workflow, its errors and credentials, and the server it runs on, and gives you a written fix plan in about 5 business days, credited toward the hardening or build.

Why n8n works in testing and breaks in production

Most n8n trouble isn't a bad workflow. It's a good workflow with nothing around it: no alert when it fails, no backup when the server goes, and no owner when the builder leaves. Five habits cover most of it.

  1. Make failures loud. One shared error workflow, set on every production workflow, that posts the workflow, the failed step and a link to the run. Add a check that fails runs which processed nothing.
  2. Back up the key with the database. n8n encrypts credentials with its encryption key. A database backup without the key means reconnecting every credential by hand.
  3. Assume every run can happen twice. Webhooks are re-sent and people re-run executions. Look records up by a unique ID before creating them.
  4. Give credentials to the company. Service accounts survive people leaving. Personal logins don't.
  5. Know your volume. A schedule every minute is about 43,200 executions a month. Price your real workload with our n8n pricing calculator, and see the n8n pricing guide for what self-hosting really costs.

Frequently asked questions

What it covers, Cloud vs self-hosted, scoring and what to do next.