Publish the content calendar with Slack and MySQL
Runs on a schedule across Slack, MySQL and WordPress, runs the text through an AI chain, then runs the custom logic in a Code node. Built for listening, around a "Normalize Post Payload" step, in 16 documented nodes.
Publish the content calendar with MySQL and WordPress in real time. An original, ready-to-import n8n workflow built around the 'Social Scheduler' pattern for marketing & advertising. It runs on a schedule and orchestrates 16 nodes across Slack, MySQL, WordPress. 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 listening, without anyone re-typing a row
- ✓A failed Slack or MySQL call is retried rather than dropped, at any of the 16 nodes in this listening build
- ✓The listening AI step is isolated from Slack, so models swap without touching the other 16 nodes
- ✓Fans the same result out to WordPress in the same run, for listening
- ✓Pinned sample data ships with it — run all 16 nodes for listening before wiring Slack
Use cases
- →Teams keeping Slack and MySQL aligned by hand for listening
- →Listening work where "Normalize Post Payload" is still a manual step before Slack
- →Listening work that only reaches Slack on a schedule, when someone remembers to start it
Integrations
Workflow preview (16 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (16 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.
- •Reading a content calendar and publishing only what is due
- •Moving data between WordPress, MySQL and Slack 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, WordPress). 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
Auto-post the content calendar: Slack for listening, scheduled
Listening on n8n: runs on a schedule across Slack, Google Sheets, MySQL and WordPress, starting at "Keep Valid Posts". Runs the text through an AI chain. 22 documented nodes.
Schedule social posts: Slack for listening
Listening on n8n: runs on a schedule across Slack, Google Sheets, MySQL and WordPress, starting at "Stamp & Shape Post". Runs the text through an AI chain. 22 documented nodes.
Auto-post the content calendar: MySQL
Cross-posting on n8n: runs on a schedule across MySQL, Slack, Google Sheets and WordPress, starting at "Normalize Post Payload". Runs the text through an AI chain. 22 documented nodes.
Publish the content calendar with Slack for cross-posting
Cross-posting on n8n: runs on a schedule across Slack, Google Sheets, MySQL and WordPress, starting at "Normalize Post Payload". Runs the text through an AI chain. 22 documented nodes.