Bidirectional GitHub workflow sync & version control for n8n workflows
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 on a schedule (every week). Along the way it connects GitHub.
How it runs
Trigger: On a schedule (every week).
- Set GitHub Details (Edit Fields (Set)): sets 3 fields: github_account_name, github_repo_name, repo_workflows_path
- n8n: uses n8n
- List files from repo (GitHub): list (file)
- n8n vs GitHub (Compare Datasets): uses Compare Datasets
- Filter: keeps only the items that match a condition
- Json file (Convert to File): converts data to a file (to json)
- If: checks a condition and branches into true / false
- Create new workflow in n8n (n8n): create
- GitHub: get (file)
- To base (Extract from File): extracts data from a file (binary to propery)
…plus 11 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 - Schedule Trigger
n8n-nodes-base.scheduleTrigger - GitHub
n8n-nodes-base.github - Convert to File
n8n-nodes-base.convertToFile - Extract from File
n8n-nodes-base.extractFromFile - Compare Datasets
n8n-nodes-base.compareDatasets - Code
n8n-nodes-base.code - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Filter
n8n-nodes-base.filter
From the author
Who is this for? This template is ideal for n8n administrators, automation engineers, and DevOps teams who want to maintain bidirectional synchronization between their n8n workflows and GitHub repositories. It helps teams keep their workflow backups…