The flow
Starts it 1Model 2Logic 5Service 5
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Google Gemini Chat ModelLm Chat Google GeminiModel
- 3ConfigurationSetLogic
- 4README GeneratorChain LlmModel
- 5Assert GitHub configIfLogic
- 6Create READMEGithubService
- 7Get a user's repositoriesGithubService
- 8Stop on empty configStop And ErrorLogic
- 9Loop Over Items READMESplit In BatchesLogic
- 10Get READMEGithubService
- 11Get LICENSEGithubService
- 12Loop Over Items LICENSESplit In BatchesLogic
- 13Create LICENSEGithubService
How it's built
- Starts on
- A clock
- Steps
- 13, with 1 branch, 2 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- GitHub
- Model
- Gemini
Questions
What does it need to run?
An n8n account, plus your own GitHub account, and a key for Gemini. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
Yes. It calls Gemini. Model calls are billed by the provider, not by n8n.
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.