n8n Error Trigger: Deduplicated Telegram Severity Alerts

Get notified only when it matters: n8n Error Trigger with deduplicated Telegram severity alerts

This n8n automation workflow captures failures from your monitored workflows, classifies them as WARNING or CRITICAL, suppresses duplicate alerts for a configurable time window, and sends clean, formatted Telegram messages to your team.

What this workflow does

• Triggers on errors whenever any workflow that has this workflow set as its n8n error workflow fails.
• Loads configuration including the Telegram chat ID, the deduplication window length, and severity keyword rules.
• Extracts key failure data such as workflow name, failed node, error message, and an execution link.
• Classifies severity by matching the error message against configured keywords:
  • CRITICAL if matched
  • WARNING otherwise
• Deduplicates repeated failures by suppressing repeated alerts for the same signature (workflow + node + first 80 characters of the message) within the configured window.
• Sends an HTML-formatted Telegram alert with automatic retries.
• Persists the alert signature in workflow static data only after the Telegram message successfully sends.

Use cases

• SaaS operators who need reliable incident visibility without Telegram spam.
• Automation engineers monitoring multiple n8n workflows where the same error can occur repeatedly in a short time.
• Teams that want severity-based routing (WARNING vs CRITICAL) to focus attention on the most urgent failures.

Technical details

• Tech stack / nodes used: set, code, telegram, sticky note, error trigger
• Integration: Telegram (via a Telegram bot token from @BotFather added as a Telegram credential in n8n)
• Deduplication storage: persistent workflow static data
• Config: Telegram chat ID, deduplication window length, and severity keywords

Setup quick guide

• Create a Telegram bot with @BotFather.
• Add the bot token as a Telegram credential in n8n.
• Set YOUR_TELEGRAM_CHAT_ID to your target chat/channel ID.
• Activate the workflow and set it as the Error workflow in Settings → Error workflow for each monitored n8n workflow.

Optional customization: swap the Telegram node for Slack, Discord, or Email, or route CRITICAL and WARNING to different destinations.