Deploy workflows from GitHub pushes to a production n8n instance
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 13 nodes and runs on Github events. Along the way it connects GitHub.
How it runs
Trigger: On Github events.
- Validate Trigger Condition (If): checks a condition and branches into true / false
- Set GitHub Repository Variables (Edit Fields (Set)): sets or maps fields
- Fetch GitHub File Content (HTTP Request): calls an HTTP API
- Set Workflow Name (Edit Fields (Set)): sets or maps fields
- Fetch All Production Workflows (HTTP Request): calls an HTTP API
- Analyze Retrieved Workflows (If): checks a condition and branches into true / false
- Set Workflow ID (Edit Fields (Set)): sets or maps fields
- Prepare JSON for Creation (Code): runs custom JavaScript code
- Retrieve n8n Workflow (HTTP Request): calls an HTTP API
- Create New n8n Workflow (HTTP Request): calls an HTTP API
…plus 2 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 (5)
- Github Trigger
n8n-nodes-base.githubTrigger - Edit Fields (Set)
n8n-nodes-base.set - HTTP Request
n8n-nodes-base.httpRequest - Code
n8n-nodes-base.code - If
n8n-nodes-base.if
From the author
Quick overview This workflow triggers on GitHub push events, fetches the changed n8n workflow JSON from the repository, cleans deployment-specific metadata, and then uses the n8n REST API to update an existing workflow or create a new one in a production n8n…