Automated workflow backup to GitHub on schedule
Needs changesNeeds changes. This template uses 1 thing(s) that n8n 3.0 removes: Convert to/from binary data. 1 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 7 nodes and runs on a schedule (every 6 hours). Along the way it connects GitHub.
How it runs
Trigger: On a schedule (every 6 hours).
- Get All Workflows (HTTP Request): calls an HTTP API
- Move Binary Data (Convert to/from binary data): uses Convert to/from binary data
- Edit a file (GitHub): edit (file)
- Get Previous FIle back (Merge): merges the data from its input branches
- If: checks a condition and branches into true / false
- Create a file (GitHub): work with file
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Convert to/from binary data in Move Binary Data: replace with Convert to File or Extract from File.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Convert to/from binary data Move Binary Data | Convert to File or Extract from File |
Nodes used (6)
- Convert to/from binary data
n8n-nodes-base.moveBinaryData - Schedule Trigger
n8n-nodes-base.scheduleTrigger - GitHub
n8n-nodes-base.github - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Merge
n8n-nodes-base.merge
From the author
Easily ensure your n8n workflows are never lost! This template automates the process of backing up all your n8n workflows to a GitHub repository every 6 hours. Set it up once and enjoy worry-free workflow versioning and disaster recovery! 🔄✨ 📝 What This…