Always Set an Error Workflow on Every Production Workflow

Every production n8n workflow should have an Error Workflow set in its settings. It runs automatically whenever an unhandled error occurs, so you can alert, log, and recover instead of losing the failure. Without one, failures are silent: they appear in the execution log, but nobody is notified. Setting it takes about 30 seconds.

What is an error workflow in n8n?

This is the single most commonly missed best practice in n8n. Every production workflow should have an Error Workflow configured in its settings. Without it, failures are silent -- they appear in the execution log, but nobody is notified. The error workflow runs automatically when any unhandled error occurs, giving you a chance to alert, log, and recover.

Real-world example: An order processing workflow fails at 2am because the payment API returns an unexpected error. Without an error workflow, the order is silently lost. With one, the on-call engineer gets a Slack message within seconds.

How do you configure an error workflow?

Configure the error workflow in the workflow settings:

# Workflow Settings (gear icon in the top-right of the editor)

Error Workflow: "Error Handler - Alert Team"

# This setting tells n8n: "If any node in this workflow throws

# an unhandled error, trigger the Error Handler workflow."

The error workflow receives an Error Trigger node with this data structure:

{
  "execution": {
    "id": "231",
    "url": "https://n8n.example.com/execution/231",
    "retryOf": null,
    "error": {
      "message": "Request failed with status code 502",
      "stack": "Error: Request failed with status code 502\n    at ..."
    },
    "lastNodeExecuted": "HTTP Request - Payment API",
    "mode": "trigger"
  },
  "workflow": {
    "id": "15",
    "name": "Order Processing Pipeline"
  }
}

Do error workflows run for manual test executions?

This does not apply to manual test executions. Error workflows only trigger for production executions (triggered by webhooks, schedules, or other triggers when the workflow is activated). Manual test runs in the editor show errors inline but do not trigger the error workflow. Test your error workflow by temporarily introducing a failure in an activated workflow.

Set this on every single production workflow. No exceptions. It takes 30 seconds and prevents silent failures from going unnoticed for hours or days.

Related: Use "Pin Data" to Freeze Node Output · Break Large Workflows into Sub-Workflows