Weekly n8n executions failures report to Telegram
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 6 nodes and runs on a schedule (every 7 days). Along the way it connects Telegram.
How it runs
Trigger: On a schedule (every 7 days).
- Get all previous executions (n8n): work with execution
- Filter: keeps only the items that match a condition
- Set a message for each failed execution (Edit Fields (Set)): sets 1 field: message
- Aggregate: combines items into one
- Telegram: uses Telegram
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 (6)
- Telegram
n8n-nodes-base.telegram - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Filter
n8n-nodes-base.filter - n8n
n8n-nodes-base.n8n - Edit Fields (Set)
n8n-nodes-base.set - Aggregate
n8n-nodes-base.aggregate
From the author
How it works - Weekly triggered - Fetches all previous executions of a given workflow - Filter for failures and aggregate them into a single report - Sends them to a given Telegram chat. Set up steps - Create a new N8N api token in the settings panel. - Add…