n8n Error Alerts to Discord + Data Table Logging

Get instant n8n failure alerts in Discord—plus automatic error logging to an n8n Data Table

This n8n automation workflow detects production workflow errors, formats a clear Discord message with the failing workflow details, posts it via a webhook, and logs key fields into an n8n Data Table for later reporting and analysis.

What this workflow does

• Triggers on failures using the Error Trigger (or supports a manual test alert via the manual trigger).
• Applies configuration such as the timezone used for timestamps.
• Formats a Discord-ready error alert including:
  • workflow name
  • last executed node
  • error message/details
  • run mode
  • timestamp
  • execution URL (when available)
• Posts to Discord using a Discord webhook with retries enabled for reliability.
• Logs failure metadata into an n8n Data Table (for example, workflow_failures) so you can track trends over time.
• Optionally forwards the payload to another n8n workflow for follow-up triage without waiting for it to complete.

Use cases

• When an automation engineer needs immediate visibility into n8n production workflow failures.
• SaaS operators want a historical view of failures using Data Table logging (workflow, failed node, error, mode, execution link).
• Teams that maintain runbooks can route alert payloads into a separate triage workflow.

Technical details

• n8n nodes/workflow pieces: set, code, discord, data table, sticky note, error trigger.
• Discord integration: Discord webhook (with retries).
• Logging: inserts key fields into an n8n Data Table.
• Execution links: requires setting N8N_EDITOR_BASE_URL so alert messages link back to your n8n editor.

Setup (quick)

• Create a Discord incoming webhook and add it to n8n credentials.
• Create/select an n8n Data Table with columns like workflow, failed_node, error, mode, and execution_url.
• Set N8N_EDITOR_BASE_URL, then select this workflow as the Error Workflow in the workflows you want to monitor.