The flow
Starts it 1Logic 7Service 7
The steps in the order they run, from what starts it.
- 1When Nightly at 2 AMSchedule triggerStarts it
- 2Set Backup ParametersSetLogic
- 3Validate Backup SettingsCodeLogic
- 4Fetch GitHub Account InfoHttp RequestService
- 5List GitHub ReposHttp RequestService
- 6Process Each RepositorySplit In BatchesLogic
- 7List S3 BackupsAws S3Service
- 8Download Repo ArchiveHttp RequestService
- 9Filter Expired BackupsCodeLogic
- 10Upload Archive to S3Aws S3Service
- 11Log Repository Backup StatusCodeLogic
- 12Check Expired BackupsIfLogic
- 13Delete Expired BackupAws S3Service
- 14Generate Backup ReportCodeLogic
- 15Send Backup Report EmailEmail SendService
How it's built
- Starts on
- A clock
- Steps
- 15, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Email, S3
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Email and S3 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. 15 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 15 steps before you point it at anything that matters.