Draft blog drafts: Slack & MySQL
Runs on a schedule across Slack and MySQL, runs the text through an AI chain, then reads the feed and keeps only what is new. Built for social copy, around a "Read Source Feed" step, in 17 documented nodes.
Draft blog drafts with MySQL and Slack automatically. An original, ready-to-import n8n workflow built around the 'Content Generation' pattern for content creation & media. It runs on a schedule and orchestrates 17 nodes across Slack, MySQL. 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. What used to take a morning now runs on its own.
Key benefits
- ✓Keeps Slack and MySQL in step for social copy, without anyone re-typing a row
- ✓Safe to re-run: records already in Slack or MySQL are skipped, across all 17 nodes of this social-copy build
- ✓A failed Slack or MySQL call is retried rather than dropped, at any of the 17 nodes in this social-copy build
- ✓Every social-copy run leaves an audit row behind, alongside Slack
- ✓The social-copy AI step is isolated from Slack, so models swap without touching the other 17 nodes
Use cases
- →Teams keeping Slack and MySQL aligned by hand for social copy
- →Social copy work where "Read Source Feed" is still a manual step before Slack
- →Social copy work that only reaches Slack on a schedule, when someone remembers to start it
Integrations
Workflow preview (17 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (17 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.
- •Chaining a writer pass and a separate critic pass for better output
- •Moving data between Slack and MySQL in a single run
- •Normalising timestamps before anything downstream compares them
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). 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
Publish social posts: Slack & MySQL for social copy
Social copy on n8n: runs on a schedule across Slack and MySQL, starting at "Prepare Approval Packet". Pauses on a Wait node until it is time to continue. 18 documented nodes.
Auto-post the content calendar: Slack for social copy, scheduled
Social copy on n8n: runs on a schedule across Slack, Google Sheets, MySQL and WordPress, starting at "Normalize Draft Payload". Runs the text through an AI chain. 22 documented nodes.
Auto-post the content calendar: Slack & MySQL
Social copy on n8n: runs on a schedule across Slack and MySQL, starting at "Read Content Calendar (MySQL)". Walks the list in batches, pausing between them. 17 documented nodes.
Auto-post the content calendar with Slack for social copy
Social copy on n8n: runs on a schedule across Slack, Google Sheets and MySQL, starting at "Normalize Draft Payload". Pauses on a Wait node until it is time to continue. 23 documented nodes.