The flow
Starts it 1Logic 12Service 10
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2ConfigSetLogic
- 3WAIT FOR MOVE TO FINISHMergeLogic
- 4GET CURRENT DATEDate TimeLogic
- 5WAIT FOR MOVE TO FINISH1MergeLogic
- 6Read/Write Files from DiskRead Write FileService
- 7Set Credential PathSetLogic
- 8Set Workflow PathSetLogic
- 9PURGE DAYSDate TimeLogic
- 10Loop Over Items1Split In BatchesLogic
- 11Execute Credential BackupExecute CommandService
- 12Execute Workflow BackupExecute CommandService
- 13LIST OLD BACKUPSDropboxService
- 14Send a text message1TelegramService
- 15UPLOAD WORKFLOWSDropboxService
- 16MergeMergeLogic
- 17CHECK DATESIfLogic
- 18GET CURRENT BACKUPSDropboxService
- 19Loop Over ItemsSplit In BatchesLogic
- 20IGNORE FOLDERSFilterLogic
- 21Send a text messageTelegramService
- 22DELETE OLD BACKUPSDropboxService
- 23MOVE INTO OLD FOLDERDropboxService
How it's built
- Starts on
- A clock
- Steps
- 23, with 1 branch, 2 loops or waits
- Size
- Large: read it before trusting it with anything live
- Connects to
- Dropbox, Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Dropbox and Telegram 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?
Take your time. At 23 steps it is large: read it before trusting it with anything live.
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 23 steps before you point it at anything that matters.