The flow
Starts it 1Logic 6Service 6
The steps in the order they run, from what starts it.
- 1Daily 7:30PMSchedule triggerStarts it
- 2ConfigCodeLogic
- 3API LoginHttp RequestService
- 4Get TabsHttp RequestService
- 5Pick Month TabsCodeLogic
- 6Read RowsHttp RequestService
- 7Desired StateCodeLogic
- 8Observe Current StateHttp RequestService
- 9Diff Desired vs ObservedCodeLogic
- 10Apply ChangeHttp RequestService
- 11ReconcileCodeLogic
- 12Build Write BatchCodeLogic
- 13Write Actions BackHttp RequestService
How it's built
- Starts on
- A clock
- Steps
- 13
- 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 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?
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.