The flow
Starts it 2Logic 9Service 4
The steps in the order they run, from what starts it.
- 1n8n Trigger (startup/restart)N8n triggerStarts it
- 2Schedule Trigger (every hour)Schedule triggerStarts it
- 3Wait (so n8n is ready and runnning)WaitLogic
- 4fetches a list of all your workflowsHttp RequestService
- 5Fetch individual workflow detailsHttp RequestService
- 6Split dataSplit OutLogic
- 7Exclude Sensitive Workflows (tag=no-backup or workflow name include INTERNALCodeLogic
- 8Loop Over ItemsSplit In BatchesLogic
- 9message of backupCodeLogic
- 10Convert to JSON & Base64 encode itCodeLogic
- 11ENDNo OpLogic
- 12GET existing FileHttp RequestService
- 13compare code nodeCodeLogic
- 14IfIfLogic
- 15Commit to GitHubHttp RequestService
How it's built
- Starts on
- A clock
- Steps
- 15, with 1 branch, 2 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- Nothing by connector; it calls services over plain HTTP
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n 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. 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.
Before you run itNothing 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.