The flow
Starts it 2Logic 6Service 4
The steps in the order they run, from what starts it.
- 1Run manuallyManual triggerStarts it
- 2Every day at 08:00 UTCSchedule triggerStarts it
- 3ConfigurationSetLogic
- 4Validate template setupCodeLogic
- 5Start ActorHttp RequestService
- 6Select current runCodeLogic
- 7Run is terminal?IfLogic
- 8Validate terminal runCodeLogic
- 9Poll same Actor runHttp RequestService
- 10Fetch exact run datasetHttp RequestService
- 11Validate and project jobsCodeLogic
- 12Upsert Google Sheets by jobKeyGoogle SheetsService
How it's built
- Starts on
- A clock
- Steps
- 12, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Google Sheets
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Sheets 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. 12 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 12 steps before you point it at anything that matters.