Multi-Channel n8n Error Alerts: Telegram, Gmail & More

Instantly notifies you of n8n workflow errors via Telegram, Gmail, and optional Discord, Slack, or WhatsApp. Provides detailed error context including message, node, time, and execution link for rapid fixes.

n8n
Multi-Channel n8n Error Alerts: Telegram, Gmail & More

The Error Notification workflow monitors your n8n instance for errors in any workflow and sends immediate alerts through multiple channels like Telegram and Gmail, with easy extensions to Discord, Slack, and WhatsApp. It captures essential details such as the error message, failing node name, timestamp, and direct link to the execution, enabling quick diagnosis and resolution without manual checks.

Key benefits include immediate awareness to prevent downtime, flexible multi-channel delivery for team notifications, and rich context for faster troubleshooting. It's built with native n8n nodes and customizable code, making it simple to integrate without complex setups. Fully open-source and free, it democratizes professional error monitoring.

Ideal for n8n developers spotting automation issues, operations teams maintaining uptime, SMBs avoiding costly tools, and enthusiasts enhancing reliability. It solves unnoticed errors by automating detection, context compilation, and delivery, slashing response times and boosting operational confidence.

Setup involves importing the workflow, configuring credentials for your channels, and activating the error trigger webhook in n8n settings.

$14.99
Last updated October 17, 2026
30-day money-back guarantee
Instant download
Lifetime updates included

New buyers can create an account from the cart to unlock a controlled $10 first-purchase credit on eligible orders of $25+.

Secure checkout powered by Stripe

Support

How to import this workflow into n8n

  1. 1Purchase or download the workflow to get the n8n workflow JSON file.
  2. 2In your n8n instance, open Workflows and choose "Import from File" (or paste the JSON with Ctrl+V on the canvas).
  3. 3Open each node marked with a credential warning and connect your own accounts and API keys.
  4. 4Run the workflow once manually to verify the data flow, then toggle it to Active.

Related Communication workflows

More from Ekaterina Mensah

Need this deployed? We'll set it up for you.

Our automation experts deploy this workflow in your stack, connect your accounts, and verify it works — or build a custom solution from scratch.