Distill documents: Slack & MySQL, webhook
Fires the moment a webhook arrives across Slack, MySQL and Telegram, pulls structured fields out of free text, then branches on the check before anything is written. Built for auto-responders, around a "Collect Raw Text" step, in 18 documented nodes.
Distill documents with MySQL and Telegram for your team. An original, ready-to-import n8n workflow built around the 'AI Summarize & Route' pattern for marketing & advertising. It fires on a webhook and orchestrates 18 nodes across Slack, MySQL, Telegram. 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. The result is a hands-off process that just works.
Key benefits
- ✓Keeps Slack and MySQL in step for auto-responders, without anyone re-typing a row
- ✓A failed Slack or MySQL call is retried rather than dropped, at any of the 18 nodes in this auto-responders build
- ✓Branches rejoin before Slack, so a auto-responders run reports once rather than 18 times
- ✓Every auto-responders run leaves an audit row behind, alongside Slack
- ✓Fans the same result out to Telegram in the same run, for auto-responders
Use cases
- →Teams keeping Slack and MySQL aligned by hand for auto-responders
- →Pushing auto-responders events into Slack and MySQL the moment they land, not on the next poll
- →Auto-responders work where "Collect Raw Text" is still a manual step before Slack
- →Auto-responders work that only reaches Slack when a webhook arrives, when someone remembers to start it
Integrations
Workflow preview (18 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (18 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.
- •Routing classified output into separate action branches
- •Rejoining parallel branches with Merge so the run reports once
- •Moving data between Telegram, MySQL and Slack in a single run
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 (Slack, MySQL, Telegram). 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
Send a daily digest: Slack & MySQL
Auto-responders on n8n: runs on a schedule across Slack, MySQL and Telegram, starting at "Read Source Feed". Runs the text through an AI chain. 18 documented nodes.
Build a weekly summary: Notion, scheduled
Auto-responders on n8n: runs on a schedule across Notion, Slack, Google Sheets, MySQL and Telegram, starting at "Gather from MySQL". Runs the text through an AI chain. 32 documented nodes.
Onboard leads: MySQL & Telegram
Auto-responders on n8n: runs on a schedule across MySQL, Telegram and Slack, starting at "Keep Valid Emails". Routes each kind of record down its own branch. 19 documented nodes.
Build a daily digest with MySQL
Inbox triage on n8n: runs on a schedule across MySQL, Telegram and Slack, starting at "Gather from MySQL". Runs the text through an AI chain. 18 documented nodes.