Automated workflow backups to GitHub with PR creation & 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 22 nodes and runs manually, when you click “Execute workflow”. Along the way it connects GitHub and Slack.
How it runs
Trigger: Manually, when you click “Execute workflow”.
- Define Local Variables (Edit Fields (Set)): sets 3 fields: branch_name, github_owner, repo_name
- n8n: uses n8n
- Get all workflows on GitHub (GitHub): list (file)
- Find new workflows (Merge): merges the data from its input branches
- Find updated workflows (Merge): merges the data from its input branches
- Get content for each workflow (GitHub): get (file)
- Wait until branch created (Merge): merges the data from its input branches
- Wait for finished (Merge): merges the data from its input branches
- Wait until branch created (Merge): merges the data from its input branches
- Base64decode workflow content (Edit Fields (Set)): sets or maps fields
…plus 10 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 (10)
- n8n
n8n-nodes-base.n8n - Merge
n8n-nodes-base.merge - HTTP Request
n8n-nodes-base.httpRequest - Edit Fields (Set)
n8n-nodes-base.set - GitHub
n8n-nodes-base.github - If
n8n-nodes-base.if - No Operation, do nothing
n8n-nodes-base.noOp - Filter
n8n-nodes-base.filter - Slack
n8n-nodes-base.slack - Manual Trigger
n8n-nodes-base.manualTrigger
From the author
Who is this for? This template is ideal for DevOps engineers, automation specialists, and n8n users who manage multiple workflows and want a reliable version control system for backups. It’s especially useful for teams collaborating via GitHub. What problem…