When you need GitHub and n8n talking to each other, here are the 65 n8n workflows in the catalog that already do it. Each is integration-tagged and privacy-stripped — copy the JSON and import.
Workflows that pair GitHub with n8n
This n8n template provides enterprise-level version control for your workflows using GitHub integration. Stop losing hours to broken workflows and manual exports – get proper commit history, visual di
This workflow backs up all non-archived n8n workflows to a GitHub repository as JSON files, using a deterministic semantic SHA in each filename to detect new, updated, renamed, and deleted workflows a
🔥 n8n Members Sale – n8n Community Members Get ideoGener8r for Just $10! (Reg. $15) Use Coupon Code: (Valid for n8n community members)
N8N-Workflow-Github-Manager. Uses github, httpRequest, n8n. Scheduled trigger; 38 nodes.
A robust workflow to back up and synchronize your n8n workflows to a GitHub repository, with intelligent change detection and support for file renames.
Git Commit. Uses github, n8n, formTrigger, httpRequest. Event-driven trigger; 34 nodes.
This template lets you selectively import n8n workflows from a GitHub repository, even when your repository uses deeply nested folder structures.
Remixed Backup your workflows to GitHub from Solomon's work. Check out his templates.
This workflow provides everything you need to package and deploy multiple workflows from a single workflow you distribute.
This workflow will backup all of your existed workflows to a single Github repository.
Say goodbye to messy JSON exports. Treat your n8n automations like real software with a built-in CI/CD pipeline.
Back Up Your N8N Workflows To Github. Uses manualTrigger, stickyNote, executeWorkflowTrigger, n8n. Event-driven trigger; 26 nodes.
This workflow will backup your workflows to Github. It uses the public api to export all of the workflow data using the n8n node.
Back Up Your n8n Workflows To Github. Uses executeWorkflowTrigger, n8n, httpRequest, github. Event-driven trigger; 26 nodes.
Code Github. Uses manualTrigger, stickyNote, n8n, httpRequest. Event-driven trigger; 25 nodes.
Based on Jonathan & Solomon work.
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 reposit
backup. Uses n8n, httpRequest, github, executeWorkflowTrigger. Event-driven trigger; 25 nodes.
Backup Workflows to GitHub. Uses n8n, httpRequest, github, executeWorkflowTrigger. Event-driven trigger; 24 nodes.
Based on Jonathan's work. Check out his templates.
Code Github. Uses manualTrigger, stickyNote, n8n, httpRequest. Event-driven trigger; 23 nodes.
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 team
Automatically backs up your workflows to Github and generates documentation in a Notion database. Weekly run, uses the "internal-infra" tag to look for new or recently modified workflows Uses a Notion
Back Up Your n8n Workflows To Github. Uses n8n, httpRequest, github, executeWorkflowTrigger. Event-driven trigger; 22 nodes.
See more GitHub workflows · n8n workflows
FAQ
How do I trigger a n8n action from GitHub?
Most workflows in this list use either a GitHub webhook trigger (real-time) or a polling trigger (every N minutes). From there, downstream n8n nodes handle the action. Open any workflow's detail page to see the exact node graph.
Do I need both a GitHub and a n8n account?
Yes — n8n connects to each integration via your own credentials. AutomationFlows strips credential IDs before publishing, so you'll add your own.
Are these GitHub → n8n workflows free?
Yes — every workflow on AutomationFlows is free to browse and copy. Pro adds a multi-signal QualityScore on every workflow plus bulk JSON download.