Weekly failures report
Configured with Aggregate, Filter, N8N, Schedule Trigger, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Messaging
- Trigger
- Routing
- Integration
- Transform
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| Telegram | Messaging | Telegram | See node parameters |
| Schedule Trigger | Trigger | Schedule Trigger | See node parameters |
| Filter for executions of the week | Routing | Filter | See node parameters |
| Get all previous executions | Integration | N8N | execution |
| Set a message for each failed execution | Transform | Edit Fields | See node parameters |
| Aggregate all messages | Transform | Aggregate | See node parameters |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
None declared. HTTP requests and Code nodes may still need configuration.
Workflow notes
👨🎤 Setup
👨🎤 Setup
You will need:
- API token to your n8n instance (settings)
- Paste the API token in new n8n credentials
- Add telegram credentials as well
Weekly failures report
Weekly failures report
This workflow will check for past executions of a given workflow and will compile and send you a list of failures which happened in the last 7 days.
Weekly failures report
Weekly failures report
Purpose and structure
This folder contains the Weekly failures report workflow. Its executable nodes use aggregate, filter, n8n, scheduleTrigger, set, telegram. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
Schedule Trigger
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Telegram/0465_Telegram_Filter_Send_Scheduled.json MIT; preserve source notices.
Canvas section labels
These name areas of the original canvas; they do not include explanatory instructions.
- 👆🏽 Set credentials to n8n here and select workflow
- 👆🏽 Set credentials to Telegram here as well as chat-id