Sync GitHub workflows to n8n after pull request merges
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 (pull request). Along the way it connects GitHub.
How it runs
Trigger: On Github events (pull request).
- Define Local Variables (Edit Fields (Set)): sets 2 fields: github_owner, repo_name
- Check if trigger event is pull request merged (Filter): keeps only the items that match a condition
- Fetch merged commit details via GitHub API (HTTP Request): calls an HTTP API
- Get files changes details (Split Out): splits a list into separate items
- Filter: keeps only the items that match a condition
- Filter: keeps only the items that match a condition
- Fetch workflow content from Git (GitHub): get (file)
- Fetch workflow content from Git (GitHub): get (file)
- Decode workflow content to json (Edit Fields (Set)): sets or maps fields
- Decode workflow content to json (Edit Fields (Set)): sets or maps fields
…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 (7)
- Edit Fields (Set)
n8n-nodes-base.set - Github Trigger
n8n-nodes-base.githubTrigger - Filter
n8n-nodes-base.filter - HTTP Request
n8n-nodes-base.httpRequest - Split Out
n8n-nodes-base.splitOut - GitHub
n8n-nodes-base.github - n8n
n8n-nodes-base.n8n
From the author
Who is this for? This template is ideal for developers, DevOps engineers, and automation managers who manage their n8n workflows using GitHub. It helps teams streamline their CI/CD automation by syncing changes from GitHub directly into n8n after a pull…