The flow
Starts it 1Logic 8Service 7
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Get first workspaceClockifyService
- 3GlobalsSetLogic
- 4Set month indexesSetLogic
- 5Split Out indexesSplit OutLogic
- 6Set intervalsSetLogic
- 7Get detailed monthly reportHttp RequestService
- 8Check if file exists in GitHubGithubService
- 9Point to new dataSetLogic
- 10Extract from FileExtract From FileService
- 11Check for 404 error messageIfLogic
- 12Compare DatasetsCompare DatasetsService
- 13Skip empty reportsFilterLogic
- 14Stop and ErrorStop And ErrorLogic
- 15Update file in GitHubGithubService
- 16Create file in GitHubGithubService
How it's built
- Starts on
- A clock
- Steps
- 16, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- GitHub
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own GitHub 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. 16 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 16 steps before you point it at anything that matters.