node cookbook
N8N GitHub Node Cookbook
Use the GitHub node to automate repository, issue, pull request, release, and team workflows from inside n8n.
Independent third-party notes. n8n is a trademark of its owner and is referenced only for compatibility and troubleshooting context.
Quick Answer
Use the GitHub node to automate repository, issue, pull request, release, and team workflows from inside n8n.
Key Facts
- Node role
- Connect n8n workflows to GitHub resources.
- Best fit
- Issue triage, PR notifications, release workflows, and repository automation.
- Credential need
- Requires GitHub credentials or OAuth/API access with suitable permissions.
- Common companion nodes
- Webhook, Slack, Linear-style tools, HTTP Request, IF, and Set.
Recommended Steps
- Configure GitHub credentials with the least scopes needed.
- Choose the GitHub resource and operation.
- Map repository owner, repo, issue, pull request, or release fields.
- Test on a sandbox repository or low-risk issue.
- Add filters so the workflow does not act on every repository event accidentally.
Verification
- The node authenticates to the intended GitHub account or app.
- A low-risk read operation returns expected repository data.
- Write operations affect only the intended repository and resource.
Warnings
- Repository automation can create comments, issues, releases, or PR changes; test with a safe repo first.
- Credential scopes should be narrow enough for the operation.
Common Mistakes
- Using broad token scopes for a narrow workflow.
- Testing write operations on production repositories.
- Forgetting organization permissions or private repository access.
- Triggering loops by reacting to the bot's own comments or changes.
Examples
GitHub trigger or scheduled issue search
IF: label includes urgent
Set: format message
Slack: notify engineering channelFAQ
Should I use GitHub node or HTTP Request?
Use the GitHub node for supported resources and operations. Use HTTP Request when you need an API endpoint or option the node does not expose.
Why does a private repo fail?
The credential may lack organization, repository, or private repo access. Check token scopes and organization authorization.