What problem does it solve?
Prevents silent failures in production n8n workflows by turning node and workflow errors into loud, structured, caller-safe responses and reliable alerting paths.
Core Features & Use Cases
- API failure handling: Ensures every fallible node error output is wired to a
Respond to Webhook so callers never see timeouts or useless success responses.
- Correct status code mapping: Routes failures to the right HTTP code class (4xx for caller issues, 5xx for your fault) and returns stable error identifiers.
- Schema validation best practices: Uses the Set IIFE schema validator pattern to produce consistent 400
validation_error bodies with actionable details.
- Transient failure self-healing: Requires network-calling nodes to use
retryOnFail to absorb 429s and brief upstream blips before triggering error handling.
- Workflow-level safety net: Guides configuration of workflow-level error workflows for unattended runs (timeouts, crashes, unwired node failures).
Quick Start
Use the n8n-error-handling skill when building your webhook endpoint so every fallible node routes its error output into a structured Respond to Webhook with the correct 4xx/5xx status code.
