The flow
Starts it 2Logic 9Service 8
The steps in the order they run, from what starts it.
- 1Lancer manuellementManual triggerStarts it
- 2Backup hebdo dim. 23h UTCSchedule triggerStarts it
- 3Configuration backupCodeLogic
- 4Lister workflows n8nHttp RequestService
- 5Extraire workflowsCodeLogic
- 6Un workflow a la foisSplit In BatchesLogic
- 7Preparer URL commitsCodeLogic
- 8Preparer backupCodeLogic
- 9GitHub Commits du jourHttp RequestService
- 10Convertir en fichierConvert To FileService
- 11Construire recap backupCodeLogic
- 12Uploader sur DriveGoogle DriveService
- 13Recap GmailGmailService
- 14GitHub Verifier fichierHttp RequestService
- 15Recap TelegramTelegramService
- 16Verifier changementCodeLogic
- 17Contenu modifie ?IfLogic
- 18Construire payload GitHubCodeLogic
- 19GitHub Pousser fichierHttp RequestService
How it's built
- Starts on
- A clock
- Steps
- 19, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Gmail, Google Drive, Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail, Google Drive and Telegram accounts. 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. 19 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 19 steps before you point it at anything that matters.