Build a metrics report: MySQL
Runs on a schedule across MySQL, Telegram and Slack, runs the text through an AI chain, then rolls the rows up into a few numbers. Built for real-time alerts, around a "Gather from MySQL" step, in 19 documented nodes.
Build a metrics report with MySQL and Telegram. An original, ready-to-import n8n workflow built around the 'Scheduled Digest' pattern for software development & devops. It runs on a schedule and orchestrates 19 nodes across MySQL, Telegram, Slack. It uses n8n's LangChain AI nodes (Agent/Chain + chat model). Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. Nothing slips through the cracks.
Key benefits
- ✓Keeps MySQL and Telegram in step for real-time alerts, without anyone re-typing a row
- ✓A failed MySQL or Telegram call is retried rather than dropped, at any of the 19 nodes in this real-time-alerts build
- ✓Branches rejoin before MySQL, so a real-time-alerts run reports once rather than 19 times
- ✓Every real-time-alerts run leaves an audit row behind, alongside MySQL
- ✓The real-time-alerts AI step is isolated from MySQL, so models swap without touching the other 19 nodes
Use cases
- →Teams keeping MySQL and Telegram aligned by hand for real-time alerts
- →Real-time alerts work where "Gather from MySQL" is still a manual step before MySQL
- →Real-time alerts work that only reaches MySQL on a schedule, when someone remembers to start it
Integrations
Workflow preview (19 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (19 nodes)
A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.
From download to running in 3 steps
- 1Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
- 2Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
- 3Activate. Run it once to test, then toggle Active. The automation is live.
What you'll learn
Advanced levelAdds branching depth and audit logging on top of the core pattern.
- •Collecting from multiple sources and blending them into one stream
- •Rolling many rows up into a few reportable numbers
- •Summarizing and formatting a readable digest
Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.
Common questions
What exactly do I get?
The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.
How do I import it into n8n?
In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.
Do I need anything else for it to work?
You need your own n8n instance and accounts/credentials for the apps this workflow connects to (MySQL, Telegram, Slack). No coding is required.
What if it doesn't work for me?
If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.
Can I modify or resell it?
You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.
Related templates
Archive key records: Notion
Helpers on n8n: runs on a schedule across Notion, Google Drive, Telegram, Slack, Google Sheets and MySQL, starting at "Export All Rows (Notion)". 30 documented nodes.
Route documents: MySQL
Approvals on n8n: runs when a form is submitted across MySQL, Telegram and Slack, starting at "Keep Valid Tasks". Routes each kind of record down its own branch. 14 documented nodes.
Review expenses: MySQL
Approvals on n8n: runs when a form is submitted across MySQL, Telegram and Slack, starting at "Keep Valid Tasks". 14 documented nodes.
Snapshot the database: Google Sheets, scheduled
Helpers on n8n: runs on a schedule across Google Sheets, Slack, MySQL, Google Drive and Telegram, starting at "Fetch Changes Since Watermark". 21 documented nodes.