The flow
Starts it 1Service 13
The steps in the order they run, from what starts it.
- 1Delete Block 1Http Request ToolService
- 2Retrieve BlockHttp Request ToolService
- 3Update Block 2Http Request ToolService
- 4Retrieve Block ChildrenHttp Request ToolService
- 5Append Block ChildrenHttp Request ToolService
- 6Retrieve CommentsHttp Request ToolService
- 7Retrieve DatabaseHttp Request ToolService
- 8Update Database 1Http Request ToolService
- 9Query DatabaseHttp Request ToolService
- 10Retrieve PageHttp Request ToolService
- 11Update Page PropertiesHttp Request ToolService
- 12Retrieve Page PropertyHttp Request ToolService
- 13Retrieve UserHttp Request ToolService
- 14Notion MCP ServerMcp triggerStarts it
How it's built
- Starts on
- An event in a connected app
- Steps
- 14
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on an event in a connected app.
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?
Plan an afternoon. 14 steps is enough that you should read each one before running it.
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.
Before you run itNothing 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 14 steps before you point it at anything that matters.