This article provides a complete, practical walkthrough of the Telegram Webhook Automation Webhook 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:  
   Automating Data Cleanup and Notifications with n8n: A Practical Workflow
   
   Meta Description:  
   Explore a powerful n8n automation workflow that cleans up outdated package data from multiple MySQL databases and sends real-time alerts via Telegram every morning or via a secure webhook. Learn how to streamline routine database maintenance with open-source efficiency.
   
   Keywords:  
   n8n workflow, MySQL automation, Telegram API, cron jobs, data cleanup automation, webhook trigger, SQL query automation, database maintenance, open-source integration, daily automated tasks
   
   Third-Party APIs Used:
   
   - Telegram API
   - MySQL (via n8n's MySQL node)
   
   —
   
   Article:
   
   In the dynamic world of logistics, e-commerce, and systems management, maintaining clean data is critical—not only for performance and storage optimization, but also for operational consistency. In this article, we dive into a practical automation use case built on n8n, a powerful open-source workflow automation tool. This particular workflow is designed to clean up old records in client databases and notify teams of actions taken via the Telegram messaging platform.
   
   Let’s break down the components of this automated process and understand how they're orchestrated to work together seamlessly.
   
   The Purpose of the Automation
   
   The primary objective of the n8n workflow is to:
   
   1. Automatically identify and clean outdated records (over one month old) in the “pacoteProduto” module with the status “TRANSPORTE-RECEBIDO” from two separate MySQL databases.
   2. Update these records by marking them with “DELETE” status.
   3. Send a notification via Telegram for each client database cleaned.
   4. Enable this operation to be triggered on a schedule (daily at 8 AM) or manually through a webhook.
   
   This ensures both clients—“Ponto Mix” and “Objetiva”—have clean datasets while keeping key personnel informed of backend operations.
   
   Key Workflow Components
   
   1. Manual Trigger & Cron Scheduler
   
   Although the workflow has a manual trigger node (disabled by default), the primary input methods are:
   
   - A Cron Node: Configured to trigger the workflow every day at 8:00 AM.
   - A Webhook Node: Accessible via a secure endpoint (path: /limparPacotes). This allows external systems or users to trigger the cleanup process on demand.
   
   2. MySQL Cleanup Queries
   
   The actual cleanup tasks are performed by two MySQL query nodes:
   
   - limpaPacoteCliente0: Connected to the “PPM” database.
   - limparPacoteCliente1: Connected to the “OBJ” database.
   
   Both execute the same SQL logic:
   
   - Use a Common Table Expression (CTE) to select tokens from the i_objeto table that meet the criteria—stored for over one month, marked as “TRANSPORTE-RECEBIDO”, and related to the module “pacoteProduto”.
   - These entries are then updated with the status “DELETE”.
   
   This separates application logic from database logic and ensures data consistency.
   
   3. Telegram Notifications
   
   Post-cleanup, two Telegram nodes send confirmation messages to a Telegram group using the Telegram API:
   
   - Message for Ponto Mix: “LIMPOU PACOTES TRANSPORTE-RECEBIDO PONTO MIX”
   - Message for Objetiva: “LIMPOU PACOTES TRANSPORTE-RECEBIDO OBJETIVA”
   
   The messages are sent to the same chat ID (a Telegram group), making team updates centralized and transparent.
   
   Why This Workflow Matters
   
   Here are a few reasons this kind of automation is game-changing:
   
   - Prevents data bloat in critical systems by regularly purging obsolete records.
   - Enhances efficiency by consolidating maintenance tasks into a single workflow.
   - Increases visibility into backend operations with automated notifications.
   - Offers scheduling flexibility with dual triggers (via cron or HTTP webhook).
   
   Expandability and Security Considerations
   
   This workflow can be scaled or modified easily:
   
   - Add more client databases by copying and adjusting additional MySQL nodes.
   - Secure the webhook with authentication parameters to prevent unauthorized execution.
   - Customize Telegram messages or routes for team-specific updates.
   
   In addition, error handling can be layered in—for instance, in the case of database connectivity issues or failed queries, alerts could be sent to a separate admin channel.
   
   Conclusion
   
   This n8n workflow showcases the practical use of automation in everyday business processes. By integrating MySQL database actions, scheduled jobs, and Telegram API notifications, what used to be a manual and repetitive task is now streamlined and reliable.
   
   Organizations striving to keep their systems lean, clean, and well-documented would benefit greatly from such workflows—especially when built in an open-source ecosystem like n8n that allows for full customization and transparency.
   
   By merging smart automation with real-time communication, businesses not only save time but also enhance operational accountability.
   
   Ready to build your first workflow like this? Dive in with n8n, and let automation work for you.

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.