n8n Error Trigger: Deduplicated Workflow Failure Alerts to Slack & Email

Stop drowning in repeated alerts—automatically send deduplicated n8n failure notifications to Slack and email

This n8n automation workflow monitors other workflows using n8n’s Error Trigger, deduplicates repeat failures within a short “quiet window,” and then sends a clear alert to Slack and optionally via SMTP email—so your team sees the signal, not the noise.

What this workflow does

• Triggers on workflow failures: It runs whenever another n8n workflow configured to use it as an “Error workflow” fails.
• Extracts the important details: It normalizes the incoming error payload to capture the workflow name, failing node (when available), the error message, and an execution URL (if available).
• Deduplicates repeated errors: If the same workflow/error repeats inside the last five minutes (quiet window), it suppresses additional alerts.
• Formats one readable alert: It builds a single Slack message and an email subject containing the workflow name, failing node (or a trigger failure note), the error text, and the execution link when provided.
• Sends alerts to your comms tools: Sends to a selected Slack channel and can also send the same content via email using SMTP.

Use cases

• SaaS operations: Notify support and engineering when critical automations fail, without spamming repeated errors.
• Automation engineering: Get actionable alerts with the failing node and execution link for faster debugging.
• Multi-workflow environments: Monitor numerous workflows from one standardized error notification pipeline.

Technical details

• Trigger: n8n Error Trigger (runs when a monitored workflow fails).
• Logic: if, set, code, and no op for normalization and quiet-window deduplication.
• Notifications: Slack (Slack API credential + target channel) and Email Send via SMTP (SMTP credentials, from/to addresses).
• Configuration: Ensure executions are saved in n8n to include execution URLs in alerts; adjust the quiet window in the code if needed.