Real-Time Workflow Error Alerting via Telegram - n8n Workflow

Highly useful for:
n8n Instance Administrators: Who need 24/7 visibility into system reliability.
DevOps Teams: Requiring real-time alerting for automated processes.
Users of complex n8n templates: Ensuring prompt remediation when critical business flows stop working.
Technical Users: Who host or manage self-hosted n8n environments.

Maintaining reliable automation is paramount. When a vital n8n workflow unexpectedly fails, immediate notification is essential to minimize downtime and data loss. This specific n8n workflow is designed to address this challenge directly. By utilizing the dedicated Error Trigger n8n node, this automation acts as a central monitoring hub for your entire n8n instance. It captures error events from any other active n8n workflow, extracts crucial details—such as the failing workflow's name and the specific error message—and routes this information instantly to your Telegram channel. This simple, yet powerful, setup ensures that your operations team receives timely alerts, making this one of the most critical n8n templates for stability and devops monitoring.

This powerful n8n workflow operates passively until an execution failure occurs anywhere else on your n8n instance.

1. Triggering the Monitor: The process begins with the specialized Error Trigger n8n trigger. Unlike standard triggers that react to external events (like webhooks or schedules), this n8n node listens internally for system errors thrown by other active workflows.


2. Data Capture: When an error occurs, the Error Trigger captures the full context of the failure, including $json.workflow.name, $json.error.message, and $json.execution.id.


3. Alert Dispatch: The captured data is immediately passed to the Telegram n8n node.


4. Notification: The Telegram n8n node formats a human-readable message, dynamically inserting the error information into the text body. This final step sends the real-time alert to the specified Telegram Chat ID, notifying the team about the critical n8n workflow failure instantly. For this setup to function, this monitoring n8n workflow must always remain active.

To deploy this critical error-monitoring n8n workflow, follow these steps:

1. Import the n8n Templates: Copy the provided JSON data and paste it into your n8n instance using the 'New' > 'Import from JSON' function.


2. Set up Telegram Credentials: You must first create a Telegram Bot via @BotFather to get your API token.


3. Configure Credentials: In your n8n Credentials setup, create a new Telegram API credential using the bot token obtained in the previous step.


4. Configure the Telegram n8n node: Open the 'Send a text message with info about error' n8n node.

1. Activate: Save and activate this error-monitoring n8n workflow. Ensure this specific n8n workflow is kept active 24/7 to capture all subsequent errors across your instance.

This compact n8n workflow relies on two key nodes:

Error Trigger (n8n trigger)
Function: This is the specialized n8n trigger that initiates the workflow. It does not run on a schedule or external request; instead, it is activated whenever any other active n8n workflow fails. It automatically collects detailed execution error data.
Key Configuration: None needed, functions automatically.

Send a text message with info about error (Telegram n8n node)
Function: Responsible for delivering the captured error message instantly to a designated Telegram chat.
Key Configuration:
Credentials: Requires a valid Telegram Bot API token credential.
Chat ID: Must contain the specific numerical ID of the recipient chat or user.
* Text: Uses expressions to inject dynamic error data, such as {{ $json.workflow.name }} (the name of the failed n8n workflow) and {{ $json.error.message }} (the error details).