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 →
{
"name": "99-error-handler",
"nodes": [
{
"id": "99000000-0000-4000-8000-000000000001",
"name": "Error terpicu",
"type": "n8n-nodes-base.errorTrigger",
"typeVersion": 1,
"position": [
260,
300
],
"parameters": {}
},
{
"id": "99000000-0000-4000-8000-000000000002",
"name": "Susun pesan",
"type": "n8n-nodes-base.code",
"typeVersion": 2,
"position": [
480,
300
],
"parameters": {
"language": "javaScript",
"jsCode": "const e = $input.first().json;\nconst workflowName = e['Workflow Name'] ?? e?.workflow?.name ?? 'N/A';\nconst lastNode = e['Last Node Executed'] ?? e?.execution?.lastNodeExecuted ?? 'N/A';\nconst errorMsg = e['Error Message'] ?? e?.execution?.error?.message ?? 'N/A';\nconst execId = e['Execution ID'] ?? e?.execution?.id ?? 'N/A';\nconst lines = [\n `\u26a0\ufe0f Error workflow: ${workflowName}`,\n `Node: ${lastNode}`,\n `Error: ${errorMsg}`,\n `ID eksekusi: ${execId}`,\n];\nreturn [{ json: { text: lines.join('\\n') } }];"
}
},
{
"id": "99000000-0000-4000-8000-000000000003",
"name": "Beri tahu admin",
"type": "n8n-nodes-base.telegram",
"typeVersion": 1.2,
"position": [
700,
300
],
"parameters": {
"resource": "message",
"operation": "sendMessage",
"chatId": "={{ $env.TELEGRAM_ADMIN_CHAT_ID }}",
"text": "={{ $json.text }}",
"additionalFields": {}
},
"credentials": {
"telegramApi": {
"name": "<your credential>"
}
}
}
],
"connections": {
"Error terpicu": {
"main": [
[
{
"node": "Susun pesan",
"type": "main",
"index": 0
}
]
]
},
"Susun pesan": {
"main": [
[
{
"node": "Beri tahu admin",
"type": "main",
"index": 0
}
]
]
}
},
"active": false,
"settings": {
"executionOrder": "v1"
},
"id": "workflow-99-error-handler"
}
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.
telegramApi
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
99-error-handler. Uses errorTrigger, telegram. Event-driven trigger; 3 nodes.
Source: https://github.com/rfaeisal/approvalsmart/blob/c079d4109c8e8b4d86ff4701b3e7c2d31cd11edb/n8n/99-error-handler.json — original creator credit. Request a take-down →
Related workflows
Workflows that share integrations, category, or trigger type with this one. All free to copy and import.
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
This workflow manages clinic appointments across Google Sheets and Google Calendar, using webhooks and Telegram to book and confirm visits, Gmail and Telegram to deliver prescriptions, scheduled Teleg
This workflow is an AI-powered roto matte generation and first-pass compositing pipeline designed for VFX production. It transforms structured roto requests into multiple high-precision matte passes u
007-Error-Handler. Uses errorTrigger, googleSheets, telegram. Event-driven trigger; 19 nodes.
05 · Error Handling & Retry Template. Uses errorTrigger, googleSheets, telegram, httpRequest. Event-driven trigger; 12 nodes.