This article provides a complete, practical walkthrough of the Telegram Filter Send Scheduled n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:
   Automate Weekly Failure Notifications with n8n and Telegram
   
   Meta Description:
   Discover how to automatically track and report workflow failures from the past 7 days using n8n. This guide walks through a powerful workflow that filters failed executions and sends a summarized report via Telegram.
   
   Keywords:
   n8n automation, workflow monitoring, n8n Telegram integration, failure notifications, automated alerts, n8n execution history, error reporting, n8n and Telegram, no-code automation, workflow failures
   
   Third-Party APIs Used:
   
   - Telegram Bot API
   
   Article:
   
   Automatically Report Workflow Failures Using n8n and Telegram
   
   In a complex automation ecosystem, things occasionally break. Whether it’s due to incorrect inputs, unresponsive third-party APIs, or logic errors, failed workloads in your automation tool can slip through the cracks—unless you're watching diligently.
   
   If you're managing mission-critical automations on n8n, monitoring failures is essential. Fortunately, with n8n's versatile no-code and low-code canvas, it's easy to track, filter, and report failures automatically.
   
   In this article, we’ll explore an n8n workflow that sends you a Telegram message every week listing all the failed executions of a specified workflow. It's a great way to maintain awareness of your automation failures without needing to log in and check manually.
   
   What This Workflow Does
   
   This n8n workflow runs on a weekly basis and performs the following steps:
   
   1. Triggers execution every 7 days.
   2. Retrieves execution history from a specific workflow.
   3. Filters out successful or outdated runs.
   4. Prepares custom failure messages for each failed run.
   5. Aggregates all messages into a single notification.
   6. Sends the summary directly to your Telegram chat.
   
   Let’s break it down.
   
   Step-by-Step Workflow Overview
   
   1. Schedule Trigger
   The workflow begins with a Schedule Trigger node set to run every 7 days. This ensures a weekly report is generated without manual intervention.
   
   2. Fetch Executions via n8n API
   Using the “n8n” node, all executions from a specific workflow are fetched. You need to set the workflow ID and authenticate with your n8n credentials. The node is configured to return all available executions.
   
   3. Filter for Weekly Failures
   Next, a filter node checks two conditions:
   - The execution started within the past 7 days (using JavaScript to calculate this via DateTime.now()).
   - The execution did not finish, indicating a failure.
   
   Only executions that meet both criteria are allowed to pass to the next stage.
   
   4. Custom Message Formatting
   Each failed execution is then passed through a Set node that constructs a human-readable message. The message contains:
   - Workflow name
   - Execution ID (with a link to inspect it directly)
   - The date/time the execution was triggered
   
   Example message:
   ⚠️ Workflow WorkflowName failed to run! [execution](12345) [date](2024-06-02T10:45:00Z)
   
   5. Aggregate the Messages
   All error messages are combined into a single text block using the Aggregate node. This way, you’re not spammed with multiple Telegram messages but get one clean summary instead.
   
   6. Notify via Telegram
   Finally, the message is sent to a specified Telegram chat using the Telegram node, configured with your bot token and the appropriate chat ID. This takes advantage of the Telegram Bot API to deliver the info where it matters most—you.
   
   Setup Instructions
   
   Before activating the workflow, you'll need to do some quick setup:
   - Add your n8n API token as a credential in the "Get all previous executions" node.
   - Specify the workflow ID for which you want to track failures.
   - Provide your Telegram bot credentials and chat ID in the Telegram node.
   Sticky Notes included in the workflow offer helpful reminders about credentials and configuration placement.
   
   Why This Workflow Is Useful
   
   - Proactive Monitoring: No need to check execution history manually.
   - Centralized Alerting: Aggregated messages make it easier to digest failure reports.
   - Automated Intelligence: Reduces human error by delivering exact execution issues to your messaging platform.
   
   Customization Opportunities
   
   You can tailor this workflow further depending on your needs:
   - Expand the trigger to a daily or custom interval.
   - Send different notifications based on the severity of the error (e.g., categorize based on error codes in the execution logs).
   - Integrate logging with email, Slack, or other alerting tools in parallel with Telegram.
   - Add retry logic based on the filtered failed executions.
   
   Conclusion
   
   Automation is only as reliable as the mechanisms monitoring it. With this intuitive n8n workflow, you can stay on top of system errors and keep your workflows healthy. Integrating the power of n8n’s low-code interface with real-time updates from Telegram ensures you're always a step ahead when something goes wrong.
   
   Try integrating this into your operational workflows today, and enjoy the peace of mind that comes with proactive failure detection.
   
   Happy automating!

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.