How do I provide my workflow to the auditor?

Simply download your n8n workflow as a JSON file and paste the content directly into the chat. The skill performs static analysis on the JSON structure to identify risks without ever needing access to your n8n instance or credentials.

Is my workflow data and API structure kept private?

Absolutely. The auditor never executes your workflow or calls your APIs; it only analyzes the configuration logic. Your JSON data stays within your secure conversation and is never shared with third parties.

How is this different from asking a standard AI to 'review my workflow'?

Unlike generic AI advice, this skill identifies specific nodes by name and provides exact parameter values (like retry intervals or timeout settings) to change. It gives you a prioritized 15-minute action plan focused on preventing business-breaking failures.

Does this work with self-hosted n8n instances or just the Cloud version?

The auditor works with any n8n workflow, regardless of whether you are on the Desktop, Self-Hosted, or Cloud version. It is designed to recognize and suggest fixes for both core nodes and common community integrations.

What exactly is included in the readiness report?

You get a comprehensive production-readiness report (scored 0–20) covering 10 critical categories including error handling, idempotency, security, and cost-trap detection, complete with node-level remediation steps.

n8n Production Readiness Auditor Skill

About this skill

Hobby workflows fail silently. Production workflows fail loudly, safely, and cheaply. This skill finds every gap between the two.

Export your n8n workflow (menu → Download), paste the JSON, and get a graded production-readiness report (0–20) across 10 categories:

Error handling — error workflows, retries, failure notifications
Credential hygiene — hardcoded secrets and API keys flagged as CRITICAL
Idempotency — will a double-fired trigger send duplicate emails or charges?
Rate limits & batching — worst-case API cost estimated in dollars and calls
Webhook security — open webhooks that mutate data are flagged as CRITICAL
Timeouts & long-running paths
Observability — will you know it worked, not just that it failed?
Data handling — what PII leaves your tenant, and how to minimize it
Naming & maintainability — because 3am debugging is real
Cost traps — tight polling, oversized LLM context, infinite-loop risk

What makes it different:

No vague advice. Every finding names the exact node, the exact setting, and the exact value — "Set retryOnFail=true, maxTries=3, waitBetweenTries=5000 on node 'Stripe - Create Charge'", never "add error handling".
Blast radius in business terms: findings tell you what actually goes wrong for your customers.
A 15-minute fix plan, ordered by damage prevented.
Static analysis only. The skill never executes your workflow or calls your services. Your JSON stays in your conversation.
Honest scoring: a solid workflow gets told it's solid.

For freelancers and agencies delivering n8n automations, and for operators who built a workflow themselves and now depend on it.

Documentation & FAQ: https://43sunsets.com/go/s1-doc-01/

Not affiliated with n8n GmbH. "n8n" is used only to describe compatibility.

N8n Production Readiness Auditor