What this workflow does
This workflow checks n8n executions for failures in the last 7 days and sends a summary report through Telegram.
It helps catch workflow problems early without needing to log in and check manually.
The report lists workflow names, execution IDs, and failure dates.
Who should use this workflow
Workflow administrators handling many automations in n8n.
Anyone who wants automatic weekly failure alerts to save time and avoid missing errors.
Tools and services used
- n8n Execution API: Retrieves workflow execution history.
- Telegram Bot API: Sends failure reports as messages.
Inputs, processing, and outputs
Inputs
- Workflow ID(s) to check executions from.
- Telegram Bot API credentials and target chat ID.
Processing steps
- Schedule triggers the workflow every 7 days.
- Retrieve all executions for specified workflow(s).
- Filter executions that failed and ran within the past 7 days.
- Create message strings with workflow name, execution ID, and failure date.
- Aggregate all messages into one combined report.
- Send aggregated message to Telegram chat.
Output
A single, readable Telegram message listing all workflow failures from the last week.
Beginner step-by-step: How to use this workflow in n8n
Importing the workflow
- Download the workflow using the Download button on this page.
- Inside the n8n editor, click Import from File and select the downloaded file.
Configuration
- Add Telegram bot API credentials in the Telegram node.
- Enter your Telegram chat ID where messages should be sent.
- In the node that retrieves executions, update the workflow ID to target the desired workflow(s).
Testing and activation
- Manually run the workflow once to check if messages arrive in Telegram.
- Fix any errors by reviewing IDs and tokens.
- Activate the workflow using the toggle in n8n for automatic weekly runs.
If self hosting n8n, see self-host n8n for help on deployment.
Customization ideas
- Monitor different workflows by changing the workflow ID in the execution node.
- Adjust how many days to look back by changing the date filter value.
- Add error details or other fields in the message template in the Set node.
- Expand notifications by adding other channels like Email or Slack nodes.
Common issues and fixes
Issue: Failure reports show empty despite errors.
Likely cause: Wrong workflow ID or incorrect date filter in nodes.
Fix: Double-check workflow ID and test date filters with sample executions.
Issue: Telegram messages do not send.
Likely cause: Invalid bot token, missing chat ID, or bot permissions.
Fix: Verify Telegram credentials and that bot has correct access to send messages.
Summary
✓ Saves time by automating weekly failure checks.
✓ Sends clear failure reports via Telegram.
✓ Helps avoid missed errors in important workflows.
✓ Easy to customize for other workflows and timeframes.
→ Provides quick visibility into workflow health without manual action.