Github
Tag
- API
Name
Github
Prerequisites
Supported authentication methods
•
API Access Token:
We use this method on all GitHub nodes.
•
OAuth2:
This method is available only on GitHub and GitHub trigger nodes, and is not used in GitHub document loaders .
Related Resources
Using API Access Tokens
There are two steps to setting up these credentials:
2.
Please see the sections below for detailed instructions.
Generate a personal access token
Recommended Access Token Types
N8n recommends using personal access tokens (classic). GitHub's fine-grained personal access tokens are still in beta and do not have access to all endpoints.
To generate a personal access token:
1.
If you haven't already, verify your email address on GitHub.
2.
3.
4.
In the left navigation, under Personal Access Tokens, select Tokens (Classic ) .
5.
Select Create New Token > Create New Token (Classic ) .
6.
Enter a descriptive name for the token in the memo field. n8n integration
7.
Select the desired expiration for the token or select No expiration .
8.
Select the token range . n8n repo for the GitHub node
Just select the range
•
Tokens that are not scoped can only access public information.
•
Reference
9.
Select Generate Token .
10.
Copy the token.
For more information, see Create a private access token (classic) . For more information about GitHub scopes, see Scopes for OAuth apps .
Set credentials
Then with your n8n credentials:
1.
If you are not using GitHub Enterprise Server, do not change your GitHub server URL.
•
2.
Enter your username as it appears on your GitHub profile .
3.
Enter the access token generated above .
