The flow
Starts it 1Logic 3Service 13
The steps in the order they run, from what starts it.
- 1⏰ Acionamento_diário.Schedule triggerStarts it
- 2📂 cria_pasta_backupGoogle DriveService
- 3📂 cria_pasta_backup1Google DriveService
- 4📋 Buscar WorkflowsHttp RequestService
- 5📁 Pasta_raizSetLogic
- 6🔗 Separa_jsonSplit OutLogic
- 7🔃 Executa_comandoExecute CommandService
- 8🔧 Formata_jsonCodeLogic
- 9📋 Lê_arquivos_bináriosRead Binary FilesService
- 10🔄️ Converte_binárioConvert To FileService
- 11🔀 Move_para_jsonMove Binary DataService
- 12💾 Salva_workflowsGoogle DriveService
- 13🔄️ Converte_binário.Convert To FileService
- 14🔎 busca_backup_-5diasGoogle DriveService
- 15💾 Salva_workflows1Google DriveService
- 16🔎 busca_backup_-2diasGoogle DriveService
- 17❌ Exclui_backup_antigo1Google DriveService
How it's built
- Starts on
- A clock
- Steps
- 17
- Size
- Medium: a working afternoon
- Connects to
- Google Drive
- 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. 17 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 17 steps before you point it at anything that matters.