Save your workflows into a GitHub repository
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 16 nodes and runs manually, when you click “Execute workflow” (plus 1 other trigger). Along the way it connects GitHub.
How it runs
Trigger: Manually, when you click “Execute workflow” (plus 1 other trigger).
- Globals (Edit Fields (Set)): sets or maps fields
- N8N Workflows (HTTP Request): calls an HTTP API
- dataArray (Function): runs custom JavaScript (legacy Function node)
- OneAtATime (Loop Over Items (Split in Batches)): loops over the items in batches
- GitHub: get (file)
- N8N Workflow Detail (HTTP Request): calls an HTTP API
- Merge: merges the data from its input branches
- isDiffOrNew (Function): runs custom JavaScript (legacy Function node)
- github_status (Switch): routes items into 3 branches
- GitHub: edit (file)
…plus 1 more step. See the full node list below.
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 dataArray, isDiffOrNew: replace with Code node, mode 'Run Once for All Items'.
- Cron in Daily @ 20:00: replace with Schedule Trigger.
| Removed in 3.0 | Replace with |
|---|---|
| Function (legacy) dataArray, isDiffOrNew | Code node, mode 'Run Once for All Items' |
| Cron Daily @ 20:00 | Schedule Trigger |
Nodes used (10)
- Manual Trigger
n8n-nodes-base.manualTrigger - Function
n8n-nodes-base.function - HTTP Request
n8n-nodes-base.httpRequest - GitHub
n8n-nodes-base.github - Merge
n8n-nodes-base.merge - Switch
n8n-nodes-base.switch - No Operation, do nothing
n8n-nodes-base.noOp - Cron
n8n-nodes-base.cron - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - Edit Fields (Set)
n8n-nodes-base.set
From the author
Basics Provides a mechanism to save all your workflows into a github repository and path (of your choosing). These can then be shared through your entire org and used to track changes (if you make any sad 'oopsies'. Flow 1. Obtains and creates listing of…