{"product_id":"n8n-error-trigger-deduplicated-telegram-severity-alerts","title":"n8n Error Trigger: Deduplicated Telegram Severity Alerts","description":"\u003ch3\u003eGet notified only when it matters: n8n Error Trigger with deduplicated Telegram severity alerts\u003c\/h3\u003e\n\u003cp\u003eThis \u003cstrong\u003en8n automation workflow\u003c\/strong\u003e captures failures from your monitored workflows, classifies them as \u003cstrong\u003eWARNING\u003c\/strong\u003e or \u003cstrong\u003eCRITICAL\u003c\/strong\u003e, suppresses duplicate alerts for a configurable time window, and sends clean, formatted \u003cstrong\u003eTelegram\u003c\/strong\u003e messages to your team.\u003c\/p\u003e\n\n\u003ch3\u003eWhat this workflow does\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eTriggers on errors\u003c\/strong\u003e whenever any workflow that has this workflow set as its \u003cstrong\u003en8n error workflow\u003c\/strong\u003e fails.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eLoads configuration\u003c\/strong\u003e including the Telegram chat ID, the deduplication window length, and severity keyword rules.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eExtracts key failure data\u003c\/strong\u003e such as workflow name, failed node, error message, and an execution link.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eClassifies severity\u003c\/strong\u003e by matching the error message against configured keywords:\n    \u003cul\u003e\n      \u003cli\u003e\n\u003cstrong\u003eCRITICAL\u003c\/strong\u003e if matched\u003c\/li\u003e\n      \u003cli\u003e\n\u003cstrong\u003eWARNING\u003c\/strong\u003e otherwise\u003c\/li\u003e\n    \u003c\/ul\u003e\n  \u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eDeduplicates repeated failures\u003c\/strong\u003e by suppressing repeated alerts for the same signature (workflow + node + first 80 characters of the message) within the configured window.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSends an HTML-formatted Telegram alert\u003c\/strong\u003e with automatic retries.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003ePersists the alert signature\u003c\/strong\u003e in \u003cem\u003eworkflow static data\u003c\/em\u003e only after the Telegram message successfully sends.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eUse cases\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eSaaS operators\u003c\/strong\u003e who need reliable incident visibility without Telegram spam.\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eAutomation engineers\u003c\/strong\u003e monitoring multiple n8n workflows where the same error can occur repeatedly in a short time.\u003c\/li\u003e\n  \u003cli\u003eTeams that want \u003cstrong\u003eseverity-based routing\u003c\/strong\u003e (WARNING vs CRITICAL) to focus attention on the most urgent failures.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eTechnical details\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003e\n\u003cstrong\u003eTech stack \/ nodes used:\u003c\/strong\u003e set, code, telegram, sticky note, error trigger\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eIntegration:\u003c\/strong\u003e Telegram (via a Telegram bot token from \u003cstrong\u003e@BotFather\u003c\/strong\u003e added as a Telegram credential in n8n)\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eDeduplication storage:\u003c\/strong\u003e persistent workflow static data\u003c\/li\u003e\n  \u003cli\u003e\n\u003cstrong\u003eConfig:\u003c\/strong\u003e Telegram chat ID, deduplication window length, and severity keywords\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003ch3\u003eSetup quick guide\u003c\/h3\u003e\n\u003cul\u003e\n  \u003cli\u003eCreate a Telegram bot with \u003cstrong\u003e@BotFather\u003c\/strong\u003e.\u003c\/li\u003e\n  \u003cli\u003eAdd the bot token as a Telegram credential in n8n.\u003c\/li\u003e\n  \u003cli\u003eSet \u003ccode\u003eYOUR_TELEGRAM_CHAT_ID\u003c\/code\u003e to your target chat\/channel ID.\u003c\/li\u003e\n  \u003cli\u003eActivate the workflow and set it as the \u003cstrong\u003eError workflow\u003c\/strong\u003e in \u003cstrong\u003eSettings → Error workflow\u003c\/strong\u003e for each monitored n8n workflow.\u003c\/li\u003e\n\u003c\/ul\u003e\n\n\u003cp\u003eOptional customization: swap the Telegram node for \u003cstrong\u003eSlack\u003c\/strong\u003e, \u003cstrong\u003eDiscord\u003c\/strong\u003e, or \u003cstrong\u003eEmail\u003c\/strong\u003e, or route CRITICAL and WARNING to different destinations.\u003c\/p\u003e","brand":"N8N Commerce","offers":[{"title":"Default Title","offer_id":46157918109875,"sku":"N8N-20371","price":26.99,"currency_code":"GBP","in_stock":true}],"thumbnail_url":"\/\/cdn.shopify.com\/s\/files\/1\/0749\/6279\/6723\/files\/i_dJq84yN6PUJo-N2jgFT_UHIEqj23.png?v=1791018221","url":"https:\/\/buyflowscripts.com\/products\/n8n-error-trigger-deduplicated-telegram-severity-alerts","provider":"N8N Commerce","version":"1.0","type":"link"}