Cron routines with Telegram
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Cron. 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 7 nodes and runs manually, when you click “Execute workflow” (plus 2 other triggers). Along the way it connects Telegram and MySQL.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 2 other triggers).
- limpaPacoteCliente (MySQL): run a query
- limparPacoteCliente (MySQL): run a query
- Telegram: uses Telegram
- Telegram: uses Telegram
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Cron: replace with Schedule Trigger.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Cron Cron | Schedule Trigger |
Nodes used (5)
- Manual Trigger
n8n-nodes-base.manualTrigger - Cron
n8n-nodes-base.cron - Telegram
n8n-nodes-base.telegram - Webhook
n8n-nodes-base.webhook - MySQL
n8n-nodes-base.mySql
From the author
Executes schedule routines, and triggers alerts via telegram