Digest long emails: MySQL + AI agent
Fires the moment a webhook arrives across MySQL, Slack and Google Sheets, hands the decision to an AI agent with its own tools, then branches on the check before anything is written. Built for newsletters, around a "Reason & Act (AI Agent)" step, in 23 documented nodes.
Digest long emails with MySQL and Telegram with instant alerts. An original, ready-to-import n8n workflow built around the 'AI Summarize & Route' pattern for marketing & advertising. It fires on a webhook and orchestrates 23 nodes across MySQL, Slack, Google Sheets. 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 MySQL and Slack in step for newsletters, without anyone re-typing a row
- ✓A failed MySQL or Slack call is retried rather than dropped, at any of the 23 nodes in this newsletters build
- ✓Bad input stops the run for newsletters instead of landing in MySQL
- ✓Branches rejoin before MySQL, so a newsletters run reports once rather than 23 times
- ✓The newsletters AI step is isolated from MySQL, so models swap without touching the other 23 nodes
Use cases
- →Teams keeping MySQL and Slack aligned by hand for newsletters
- →Newsletters work that needs a judgement call per item before it reaches MySQL
- →Pushing newsletters events into MySQL and Slack the moment they land, not on the next poll
- →Newsletters work where "Reason & Act (AI Agent)" is still a manual step before MySQL
Integrations
Workflow preview (23 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (23 nodes)
A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.
Agent tools included (2)
An AI Agent is only as capable as the tools wired into it. These are read from the template's own graph — every one is a real node in the file you download.
- Run Calculations · Calculator
- Think It Through · Scratchpad reasoning
Conversation memory is attached, so the agent carries earlier turns of a session.
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
Production levelProduction-grade: idempotency, dead-letter handling, and reconciliation included.
- •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 (MySQL, Slack, Google Sheets, 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
Onboard subscribers with MySQL
Newsletters on n8n: runs on a schedule across MySQL, Slack, Google Sheets and Telegram, starting at "Normalize Email Payload". Routes each kind of record down its own branch. 22 documented nodes.
Compile a weekly summary for newsletters
Newsletters on n8n: runs on a schedule across Google Sheets, MySQL, Telegram and Slack, starting at "Pull Fresh Items (API)". Summarises long text with an AI chain. 24 documented nodes.
Re-engage upcoming appointments: MySQL, scheduled
Newsletters on n8n: runs on a schedule across MySQL, Google Sheets, Slack, Notion and Telegram, starting at "Read Pending Queue (MySQL)". 30 documented nodes.
Deliver a weekly summary: Google Sheets & Slack
Newsletters on n8n: runs on a schedule across Google Sheets, Slack, Telegram and MySQL, starting at "Pull Fresh Items (API)". Summarises long text with an AI chain. 24 documented nodes.