Error Handling in n8n Production

In production environments, APIs will fail, networks will experience downtime, and webhooks will pass malformed payloads. Without robust error handling, failed workflows can block critical pipelines silently.

1. Using Retry Settings on Nodes

n8n allows you to configure automatic retries directly on individual nodes. Click on the cog settings icon inside any node and configure:

• Always Output Data: Ensures the node outputs an empty json object instead of throwing an error.
• On Fail: Retry 3 times, with an interval of 5000ms.

2. Global Error Trigger Workflows

Instead of configuring fallback branches for every node, you can create a dedicated **Error Trigger Workflow**. This workflow launches automatically whenever *any* node inside any other active workflow fails.

The Error Trigger node outputs metadata containing the execution ID, the workflow name, and the specific error message, which you can format and send to Slack or PagerDuty.