n8n Error Workflow Template: What Production Alerts Actually Need

Minimum fields to normalize

• Workflow name and failure timestamp.
• Failed node when available.
• Execution ID and execution URL when available.
• Privacy-safe error summary.
• Whether the run is a retry of an earlier execution.

Do not assume every execution field exists. Trigger-level failures can arrive with a different error shape.

Recommended flow

1. Start with n8n's Error Trigger.
2. Normalize the incoming payload into a fixed incident schema.
3. Classify whether the error is transient, authentication-related, validation-related, or unknown.
4. Alert a human with the failed workflow, node and execution link.
5. Retry only when duplicate safety and external side effects are understood.

Do not automate these mistakes

• Blindly retrying 401/403 authentication errors.
• Replaying a partially completed workflow before checking CRM, email, invoice or webhook side effects.
• Sending raw credentials, tokens or customer payloads into alerts.
• Relying on the error workflow alone to detect a trigger that never fired.

Production acceptance test

• Create one controlled automatic failure and confirm the error workflow runs.
• Verify the alert remains readable when an execution URL is absent.
• Confirm duplicate-protected actions execute no more than once during recovery.
• Test an independent heartbeat for revenue-critical triggers.