The flow
Starts it 1Logic 11Service 4
The steps in the order they run, from what starts it.
- 1Weekly Schedule TriggerCronStarts it
- 2Set: Repository ConfigurationSetLogic
- 3Get Branch DetailsHttp RequestService
- 4Get Repository File ListHttp RequestService
- 5Process Each File SeparatelySplit OutLogic
- 6check file IF: .kt or .javaIfLogic
- 7Download File ContentHttp RequestService
- 8Read Files One by OneSplit In BatchesLogic
- 9Decode File ContentCodeLogic
- 10Extercet key flagsCodeLogic
- 11Filter keysCodeLogic
- 12classify keyCodeLogic
- 13Mock Firebase Flags DataSetLogic
- 14Code: Compare FlagsCodeLogic
- 15Create Final Summary ReportCodeLogic
- 16Send Slack ReportSlackService
How it's built
- Starts on
- A clock
- Steps
- 16, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack 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.