The flow
Starts it 2Logic 7Service 8
The steps in the order they run, from what starts it.
- 1When clicking ‘Test workflow’Manual triggerStarts it
- 2Send_Backup_NotificationTelegramService
- 3DailySchedule triggerStarts it
- 4Backup_ConfigCodeLogic
- 5Get_WorkflowsHttp RequestService
- 6Clean_WorkflowsCodeLogic
- 7Create_Backup_PackageCodeLogic
- 8Check_Repository_ExistsHttp RequestService
- 9If_Repo_Not_ExistsIfLogic
- 10Create_RepositoryHttp RequestService
- 11Upload_ManifestHttp RequestService
- 12Upload_READMEHttp RequestService
- 13Split_Workflow_FilesCodeLogic
- 14Loop_Workflow_UploadsSplit In BatchesLogic
- 15Backup_Complete_SummaryCodeLogic
- 16Upload_Workflow_FilesHttp RequestService
- 17Gmail - NotificationGmailService
How it's built
- Starts on
- A clock
- Steps
- 17, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Gmail, Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Gmail 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?
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.