n8n error alerts that don't spam you: Error Trigger + dedupe (n8n 2.x)

Description and use

Implemented an n8n error workflow that sends a single alert per failure and suppresses duplicates for 30 minutes, requiring the workflow to be published in n8n 2.x.

Problem

n8n does not notify when a workflow fails unless configured, leading to repeated alerts for the same error.

Outcome

Implemented a single‑alert error workflow that deduplicates repeated failures within a 30‑minute window and requires publishing in n8n 2.x to function.

Workflow

• Create a workflow named "Error alert router".
• Add an Error Trigger node to receive failure details.
• Add a Code node that formats the message and implements deduplication using static data.
• Add an alert node (Slack, Discord, Telegram, or Send Email).
• Publish the error workflow (must be active in n8n 2.x).
• Configure each workflow’s settings to point to the "Error alert router" error workflow.
• Test by creating a throwaway workflow that throws an error and executing it via webhook.

Evidence

n8n doesn't tell you when a workflow fails unless you ask it to.

Source

In n8n 2.x the error workflow must be published (active). We tested this on 2.40.6.

Source

After publishing, the same failure produced exactly one alert, and two identical follow-up failures were suppressed.

Source