n8n-error-handling
Design visible, structured, recoverable n8n failures using error outputs, retries, Error Trigger workflows, and HTTP error responses.
Profile →npx skills add sickn33/agentic-awesome-skills --skill n8n-error-handling --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# n8n Error Handling ## When to Use Use this skill for unattended workflows, webhook/API response contracts, retry design, error outputs, Error Trigger workflows, alerting, or any path where failure must be visible and recoverable. Make retries bounded and idempotent, especially for sends, payments, and writes. Redact credentials, personal data, request bodies, and stack details from caller-facing responses and alerts; expose only the minimum diagnostic context required. By default, when an n8n node throws, the **whole workflow halts**. For an interactive run you're watching, that's fine — you see the red node and fix it. For anything unattended (a webhook API, a cron job, a queue worker, an agent tool), it's the wrong default: the caller gets a timeout or an empty 500, the operator gets no alert, and the symptom is "the integration just stopped working" with no log and no clue. This skill is about making failures **loud, structured, and recoverable** — and, best case, **self-healing** so transient blips never reach a human at all. The two ideas that prevent most silent failures: - **Per-node error outputs** — a node's failure routes down a second output you control, instead of kil
- When to Use
- When you actually need this
- The #1 silent trap: per-node error output is a TWO-step setup
- Doing both with n8nupdatepartialworkflow
- Self-healing first: retryOnFail before you wire error paths
- API workflows: the canonical shape
- Input validation: the Set-node schema validator
- Response shapes: map cause → status code
- Workflow-level error workflow (the catch-all)
- What's NOT available via the community MCP
- Anti-patterns
- Reference files
- Integration with other skills
- Quick reference checklist
What does the n8n-error-handling skill do?
Design visible, structured, recoverable n8n failures using error outputs, retries, Error Trigger workflows, and HTTP error responses.
How do I install it?
Run `npx skills add sickn33/agentic-awesome-skills --skill n8n-error-handling --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From sickn33/agentic-awesome-skills, a repository with 44,414 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.