Automatic backup of workflows to GitHub with email/telegram notifications
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 17 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects Telegram and Gmail.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Backup_Config (Code): runs custom JavaScript code
- Get_Workflows (HTTP Request): calls an HTTP API
- Clean_Workflows (Code): runs custom JavaScript code
- Create_Backup_Package (Code): runs custom JavaScript code
- Check_Repository_Exists (HTTP Request): calls an HTTP API
- If: checks a condition and branches into true / false
- Create_Repository (HTTP Request): calls an HTTP API
- Upload_Manifest (HTTP Request): calls an HTTP API
- Upload_README (HTTP Request): calls an HTTP API
- Split_Workflow_Files (Code): runs custom JavaScript code
…plus 5 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Manual Trigger
n8n-nodes-base.manualTrigger - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Telegram
n8n-nodes-base.telegram - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Gmail
n8n-nodes-base.gmail
From the author
Why? Have you ever updated your n8n instance, or moved from one instance to the other and lost all your workflows? I suggest NOT DOING THAT! Especially if you have very complex workflows that would take days to recreate. Make sure you have a backup process in…