Monitor workflow health using n8n execution history and Telegram alerts
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 11 nodes and runs on a schedule (every 6 hours). Along the way it connects Telegram and Slack.
How it runs
Trigger: On a schedule (every 6 hours).
- Fetch Active Workflows (n8n): uses n8n
- Filter Active Workflows (Code): runs custom JavaScript code
- Loop Over Workflow Batches (Loop Over Items (Split in Batches)): loops over the items in batches
- Generate Health Report (Code): runs custom JavaScript code
- Retrieve Workflow Details (n8n): get
- Check for Alerts (If): checks a condition and branches into true / false
- Fetch Recent Executions (n8n): work with execution
- Send Telegram Alert (Telegram): uses Telegram
- Send a message (Slack): uses Slack
- Evaluate Workflow Health (Code): runs custom JavaScript code
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (7)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - n8n
n8n-nodes-base.n8n - Code
n8n-nodes-base.code - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - If
n8n-nodes-base.if - Telegram
n8n-nodes-base.telegram - Slack
n8n-nodes-base.slack
From the author
Quick overview This workflow runs every 6 hours to audit your n8n instance by listing active workflows, reviewing their latest execution history, and compiling a health report, optionally sending alerts to Telegram when failures, repeated errors, or overdue…