AutomationFlowsSlack & Telegram › n8n Error Alerts to Telegram (3 Nodes)

n8n Error Alerts to Telegram (3 Nodes)

Original n8n title: Error to Tg

Error To TG. Uses start, errorTrigger, telegram. Event-driven trigger; 3 nodes.

Event trigger★☆☆☆☆ complexity3 nodesStartError TriggerTelegram
Slack & Telegram Trigger: Event Nodes: 3 Complexity: ★☆☆☆☆ Added:

This workflow follows the Error Trigger → Telegram recipe pattern — see all workflows that pair these two integrations.

The workflow JSON

Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →

Download .json
{
  "name": "Error To TG",
  "nodes": [
    {
      "parameters": {},
      "name": "Start",
      "type": "n8n-nodes-base.start",
      "typeVersion": 1,
      "position": [
        240,
        300
      ]
    },
    {
      "parameters": {},
      "name": "Error Trigger",
      "type": "n8n-nodes-base.errorTrigger",
      "typeVersion": 1,
      "position": [
        860,
        580
      ]
    },
    {
      "parameters": {
        "chatId": "@pseudoyuchat",
        "text": "=<b>n8n workflow error</b> #n8n-error\n<a href=\"{{$json[\"execution\"][\"url\"]}}\">{{$json[\"workflow\"][\"name\"]}}</a>\n\nError: <code>{{$json[\"execution\"][\"error\"][\"message\"]}}</code>\n<pre><code>{{$json[\"execution\"][\"error\"][\"stack\"]}}</code></pre>",
        "additionalFields": {
          "disable_web_page_preview": true,
          "parse_mode": "HTML"
        }
      },
      "name": "Telegram",
      "type": "n8n-nodes-base.telegram",
      "typeVersion": 1,
      "position": [
        1080,
        580
      ],
      "credentials": {
        "telegramApi": {
          "name": "<your credential>"
        }
      }
    }
  ],
  "connections": {
    "Error Trigger": {
      "main": [
        [
          {
            "node": "Telegram",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "active": false,
  "settings": {},
  "id": 9,
  "tags": []
}

Credentials you'll need

Each integration node will prompt for credentials when you import. We strip credential IDs before publishing — you'll add your own.

Pro

For the full experience including quality scoring and batch install features for each workflow upgrade to Pro

About this workflow

Error To TG. Uses start, errorTrigger, telegram. Event-driven trigger; 3 nodes.

Source: https://github.com/caioross/n8n_Workflows/blob/1686b66af0462dfce267af508b0a487aa5f41e18/workflows/Error_To_TG.json — original creator credit. Request a take-down →

More Slack & Telegram workflows → · Browse all categories →

Related workflows

Workflows that share integrations, category, or trigger type with this one. All free to copy and import.

Slack & Telegram

Report N8N Workflow Errors To Telegram. Uses errorTrigger, stickyNote, telegram. Event-driven trigger; 5 nodes.

Error Trigger, Telegram
Slack & Telegram

Error workflows are an important part of running workflows in production. Make sure to set them up for all your important workflows. The message links directly to the execution. Add Telegram creds Set

Error Trigger, Telegram
Slack & Telegram

Error Handler send Telegram. Uses telegram, errorTrigger, stickyNote. Event-driven trigger; 4 nodes.

Telegram, Error Trigger
Slack & Telegram

99_global_error_handler. Uses errorTrigger, telegram, googleSheets, stickyNote. Event-driven trigger; 4 nodes.

Error Trigger, Telegram, Google Sheets
Slack & Telegram

clients kept booking meetings during my prayer times. i'd either miss a prayer or scramble to reschedule. the problem wasn't the clients — it was that my calendar had no blocked windows for salah. i n

Telegram Trigger, HTTP Request, Google Calendar +3