Backup workflows to GitHub
Needs changesNeeds changes. This template uses 2 thing(s) that n8n 3.0 removes: Function (legacy), Cron. 2 breaking item(s) found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 11 nodes and runs on a schedule (legacy Cron node). Along the way it connects GitHub.
How it runs
Trigger: On a schedule (legacy Cron node).
- Get workflows (HTTP Request): calls an HTTP API
- transform (Function): runs custom JavaScript (legacy Function node)
- Get workflow data (HTTP Request): calls an HTTP API
- Merge: merges the data from its input branches
- Merge: merges the data from its input branches
- Create file (GitHub): work with file
- GitHub: edit (file)
- Get Files (GitHub): get (file)
- Transform (Function): runs custom JavaScript (legacy Function node)
- Download Raw Content (HTTP Request): calls an HTTP API
Services it uses
Before you upgrade to n8n 3.0
2 things in this workflow are removed in n8n 3.0. Fix them before you upgrade:
- Function (legacy) in Transform, transform: replace with Code node, mode 'Run Once for All Items'.
- Cron in Daily at 23:59: replace with Schedule Trigger.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) Transform, transform | Code node, mode 'Run Once for All Items' |
| Cron Daily at 23:59 | Schedule Trigger |
Nodes used (5)
- GitHub
n8n-nodes-base.github - Function
n8n-nodes-base.function - Merge
n8n-nodes-base.merge - HTTP Request
n8n-nodes-base.httpRequest - Cron
n8n-nodes-base.cron
From the author
Note: This workflow uses the internal API which is not official. This workflow might break in the future. The workflow executes every night at 23:59. You can configure a different time bin the Cron node. Configure the GitHub nodes with your username, repo…