The flow
Starts it 2Logic 6Service 10
The steps in the order they run, from what starts it.
- 1Daily Backup TriggerSchedule triggerStarts it
- 2When clicking ‘Test workflow’Manual triggerStarts it
- 3Extract MySuperAuth TokenExecute CommandService
- 4Configure Git RepositorySetLogic
- 5Check Local RepositoryExecute CommandService
- 6Check Repository ExistenceIfLogic
- 7Fetch All WorkflowsN8nService
- 8Clone Git RepositoryExecute CommandService
- 9Process WorkflowsSplit In BatchesLogic
- 10Want to Export Credentials ?IfLogic
- 11Export Current WorkflowExecute CommandService
- 12Export CredentialsExecute CommandService
- 13Wait For All ExportsWaitLogic
- 14Rename Workflow FilesExecute CommandService
- 15Stage ChangesExecute CommandService
- 16Any Change in the WorkflowsIfLogic
- 17Commit ChangesExecute CommandService
- 18Push to Remote RepositoryExecute CommandService
How it's built
- Starts on
- A clock
- Steps
- 18, with 3 branches, 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. 18 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 18 steps before you point it at anything that matters.