The flow
Starts it 1Logic 9Service 3
The steps in the order they run, from what starts it.
- 1When clicking ‘Execute workflow’Manual triggerStarts it
- 2Set VariablesSetLogic
- 3Switch API VersionSwitchLogic
- 4Confluence - Get Outdated Spaces via CQLHttp RequestService
- 5Confluence - Get SpacesHttp RequestService
- 6Split Out Pages V1Split OutLogic
- 7Format Space IdsSetLogic
- 8Set Report Data V1SetLogic
- 9Confluence - Get PagesHttp RequestService
- 10AggregateAggregateLogic
- 11Split Out Pages V2Split OutLogic
- 12Filter Version by cutoffDateFilterLogic
- 13Set Report Data V2SetLogic
How it's built
- Starts on
- An event in a connected app
- Steps
- 13, with 1 branch
- 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. 13 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.
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 13 steps before you point it at anything that matters.