The flow
Starts it 1Logic 11Service 6
The steps in the order they run, from what starts it.
- 1Daily Backup TriggerSchedule triggerStarts it
- 2Set ConfigurationSetLogic
- 3Config ValidationCodeLogic
- 4Get All n8n WorkflowsHttp RequestService
- 5Split WorkflowsSplit OutLogic
- 6Process Each WorkflowSplit In BatchesLogic
- 7Backup scope all?IfLogic
- 8Prepare WorkflowCodeLogic
- 9Backup scope active?IfLogic
- 10Generate Workflow HashCryptoService
- 11If workflow active?IfLogic
- 12Backup scope tagged?IfLogic
- 13Lookup Workflow in Data TableData TableService
- 14Workflow Exists?IfLogic
- 15Hash Changed?IfLogic
- 16Upload New Workflow BackupGoogle DriveService
- 17Delete Existing Workflow BackupGoogle DriveService
- 18Upsert Workflow RecordsData TableService
How it's built
- Starts on
- A clock
- Steps
- 18, with 6 branches, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Google Drive, n8n data table
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Drive 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.
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 18 steps before you point it at anything that matters.