Skip to content
SkillModel-led4,996 tokens in use

n8n Error Handling

A guide to n8n error handling: the two-step per-node error output, retryOnFail, 4xx and 5xx webhook responses and Error Trigger workflows for unattended runs.

6,686 stars on the repository MIT Licenseczlonkowski/n8n-skills · skills/n8n-error-handling
/plugin install czlonkowski/n8n-skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing n8n Error Handling costs

128tokens idle
4,996tokens in use
15,907tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples12/15
  • Output15/15
  • Size15/15
  • Resources12/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity88
  • Maintenance92
  • Community60
  • Maturity36
  • Momentum40

n8n Error Handling is a skill for Claude that makes workflow failures loud, structured and recoverable. By default one failing node halts an n8n workflow and the caller of a webhook sees a timeout or an empty 500, so unattended and API workflows need explicit handling.

The skill covers the two-step setup for per-node error outputs, node retries, the status codes and response bodies a webhook should return, input validation, and a separate Error Trigger workflow that alerts someone when something escapes. It also lists the failures an error output never sees.

What You Get

  • A table of which workflow shapes need error handling and which can skip it
  • The two-step recipe: set onError to continueErrorOutput, then wire main[1], with patch operations for both
  • A retryOnFail recipe with its engine limits
  • A cause-to-status table for 400, 401, 403, 404, 409, 429, 500, 502, 503 and 504, with a Switch layout
  • An Error Trigger workflow outline with the recursion trap and the handled-error trap
  • Reference files for node error outputs, API workflows, response shapes and error workflows

Common Use Cases

  • Hardening a webhook API so each failure returns a clear status and body
  • Adding retries and an alert workflow to a scheduled sync
  • Finding why a run shows success although a node’s error was discarded
  • Validating input upstream and returning field-level 400 responses
  • Reviewing a workflow where the error branch returns 200

What Makes It Unique

It names the half-wired error output as the top silent trap, with a table of what happens in each half-done state, and it says validate_workflow will not catch it, so Claude pulls the workflow to confirm both parts. It lists failures that bypass error outputs, such as errors inside expressions, and it states what the MCP cannot set, so Claude hands the user the UI step for the error workflow.

Under The Hood

The skill is instructions and four reference markdown files, with no scripts. It tells Claude to patch node settings and connections, validate, autofix, run test executions and read executions through the n8n-mcp tools, all of which call your n8n server. The workflows it builds can post alerts to Slack or email when they run, and the skill reminds the user to assign the error workflow in the n8n settings screen.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers