The flow
Starts it 1Logic 12Service 11
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Get all blog posts1NotionService
- 3Is sync checked?1FilterLogic
- 4Slug uniqueness checker and differentiator1CodeLogic
- 5For each blog post1Split In BatchesLogic
- 6Success message1SlackService
- 7Get simple page dataNotionService
- 8Get all page dataNotionService
- 9Merge1MergeLogic
- 10Take cover urlSetLogic
- 11Final Notion post dataMergeLogic
- 12Get blocks1NotionService
- 13Data transporter, Notion posts to sync1No OpLogic
- 14Get all collection posts1WebflowService
- 15Turn blocks into HTML1CodeLogic
- 16Compare by slug1Compare DatasetsService
- 17Craft the rich text element1CodeLogic
- 18Create post1WebflowService
- 19Merge2MergeLogic
- 20Add Webflow item id to Notion dataCodeLogic
- 21Add slug to posts1NotionService
- 22Update in "Blog Posts"WebflowService
- 23Data transporter1No OpLogic
- 24Update slug on posts1NotionService
How it's built
- Starts on
- A clock
- Steps
- 24, 1 loop or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- Notion, Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Notion and Slack accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Take your time. At 24 steps it is large: read it before trusting it with anything live.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 24 steps before you point it at anything that matters.