Get a weekly Telegram digest of failed runs for any workflow you choose. It helps ops and platform teams spot issues early without digging through logs. Great for teams that want a simple health check in chat.

A schedule runs every seven days. The n8n Executions node pulls the full run history for the selected workflow. A filter keeps only items from the last week and failed status. A Set step builds a short line for each failure with the workflow name and a link to the run. An Aggregate node collects all lines into one message, and the Telegram node posts it to your chat.

You need an n8n API token, a Telegram bot token, and the chat id. After connecting, pick the workflow to monitor and adjust the timing if needed. Expect fewer missed failures and faster follow up during weekly reviews and standups.

• Weekly schedule trigger that you can change to any interval you prefer
• n8n Executions API pulls all runs for the selected workflow
• Date filter keeps only runs from the last seven days and failed status
• Set node formats a readable line with workflow name and execution link
• Aggregate node compiles all lines into one message for easy reading
• Telegram node sends the digest to your chosen chat id

• Reduce manual log reviews from 60 minutes to under 5 minutes each week
• Automate 100% of weekly failure checks with a single scheduled run
• Send one clear summary to the right chat so the team can act fast
• Scale to many workflows by duplicating the template and switching the workflow id
• Connect n8n and Telegram without custom code

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Telegram. See the Tools Required section above for links to create accounts with these services.
3. In n8n Cloud, create an API token: Open Settings > API > Create Token, then copy the token.
4. Open the Get all previous executions node. In the Credential to connect with dropdown, click Create new credential, select n8n API or similar, and paste your API token. Give the credential a clear name like n8n API Production.
5. Still in the Get all previous executions node, choose the workflow to monitor in the workflowId field so the query returns runs for that workflow only.
6. Open the Telegram node. In the Credential to connect with dropdown, click Create new credential, then follow the on screen instructions to integrate that service. Provide your bot token when asked.
7. Enter your Telegram chat id in the Telegram node. Send a test message to your bot to confirm the chat id is correct.
8. Adjust the Schedule Trigger if you want a different cadence. For testing, temporarily switch it to run every minute, then switch back to weekly.
9. Activate the workflow and wait for the next run. If the chosen workflow has failures in the last seven days, you should receive a digest in Telegram.
10. Troubleshooting: If no message arrives, check that the workflowId is set, the API token is valid, the Telegram chat id is correct, and that there are failed runs within the last seven days. Review the Execution log in n8n for any errors.