The flow
Starts it 2Logic 15Service 12
The steps in the order they run, from what starts it.
- 1When clicking ‘Execute workflow’Manual triggerStarts it
- 2Schedule TriggerSchedule triggerStarts it
- 3VariablesCodeLogic
- 4Get SourcesNotionService
- 5Apify PayloadCodeLogic
- 6Run an ActorApifyService
- 7Get StatusApifyService
- 8SwitchSwitchLogic
- 9Get dataset itemsApifyService
- 10WaitWaitLogic
- 11Map ReelsCodeLogic
- 12Owner?IfLogic
- 13Update AccountsNotionService
- 14Many to OneCodeLogic
- 15Get ReelsNotionService
- 16CodeCodeLogic
- 17Loop Over ItemsSplit In BatchesLogic
- 18StatsCodeLogic
- 19Is Created?SwitchLogic
- 20Download VideoHttp RequestService
- 21UpdateNotionService
- 22Upload to GeminiHttp RequestService
- 23Processing DelayWaitLogic
- 24Get File StateHttp RequestService
- 25Is Uploaded And Active?IfLogic
- 26Set PromptSetLogic
- 27Gemini AnalyzeHttp RequestService
- 28Format ResponseCodeLogic
- 29CreateNotionService
How it's built
- Starts on
- A clock
- Steps
- 29, with 4 branches, 3 loops or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- Apify, Notion
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Apify and Notion 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 29 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 29 steps before you point it at anything that matters.