Daily workflow backups to GitHub with Slack 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 16 nodes and runs on a schedule (every day). Along the way it connects GitHub and Slack.
How it runs
Trigger: On a schedule (every day).
- Starting Message (Slack): uses Slack
- Config (Edit Fields (Set)): sets 4 fields: repo_owner, repo_name, repo_path…
- Get Workflows (n8n): uses n8n
- Filter: keeps only the items that match a condition
- Loop Over Items (Loop Over Items (Split in Batches)): loops over the items in batches
- Completed Notification (Slack): uses Slack
- Get a file (GitHub): get (file)
- Merge: merges the data from its input branches
- Is File too large? (If): checks a condition and branches into true / false
- isDiffOrNew (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 (12)
- Edit Fields (Set)
n8n-nodes-base.set - Merge
n8n-nodes-base.merge - Code
n8n-nodes-base.code - GitHub
n8n-nodes-base.github - Filter
n8n-nodes-base.filter - Switch
n8n-nodes-base.switch - n8n
n8n-nodes-base.n8n - Schedule Trigger
n8n-nodes-base.scheduleTrigger - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - Slack
n8n-nodes-base.slack - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches
From the author
Who is this for? This workflow is ideal for n8n self-hosted users, DevOps engineers, and automation developers who want to automatically back up their n8n workflows to GitHub on a regular basis. What problem is this workflow solving Manually backing up n8n…