n8n Error Trigger to Slack Alerts + Discord Fallback

Get instant failure alerts in Slack—without losing them

This n8n workflow listens for errors from any other workflow using n8n’s built-in Error Trigger, posts a clear failure summary to Slack, and automatically falls back to Discord if the Slack notification fails. Perfect for keeping your operations informed when automations break.

What this workflow does

• Catches workflow failures from n8n’s Error Trigger and receives key details: workflow name, failing node, error message, and the execution URL.
• Prevents duplicate alerts by checking whether the exact execution was already notified—helpful for multi-failure scenarios.
• Formats a readable error summary and sends it to Slack using an Incoming Webhook (no Slack app or OAuth required).
• Fails over to Discord: if the Slack HTTP request fails for any reason, the workflow posts the same summary to Discord via an Incoming Webhook instead of silently losing the alert.

Use cases

• SaaS operators monitoring critical background jobs (e.g., syncs, scheduled automations) who need immediate visibility when executions fail.
• Automation engineers debugging workflow issues faster with direct links to the failing execution.
• Teams with Slack-heavy ops who still want guaranteed notification coverage via Discord if Slack webhook delivery encounters problems.

Technical details

• Trigger: n8n Error Trigger
• Logic & flow control: if, set, code, no op, plus documentation/notes nodes (sticky note)
• Integrations: Slack Incoming Webhook + Discord Incoming Webhook via HTTP Request nodes

Setup (quick)

• Create a Slack Incoming Webhook URL and paste it into the node: “Set: Slack webhook URL”.
• Create a Discord Incoming Webhook URL and paste it into the node: “Set: Discord webhook URL”.
• Activate this workflow, then for workflows you monitor go to Settings → Error Workflow and select this workflow.