Connect GitHub

≈ 3 min Extension Application web Bearer Token

Before you start

• A GitHub account with access to the repositories.

Used by

• GitHub

Pick a method

Method	Use it when
Fine-grained token Recommended	Limited to chosen repositories and permissions. The safest choice.
Classic token	Older tokens that open your whole account. Use only if fine-grained tokens are blocked in your organization.

Set it up

Fine-grained token (recommended)

1. Create the token. On GitHub, open Settings › Developer settings › Personal access tokens › Fine-grained tokens and click Generate new token.

2. Limit it. Pick the Resource owner, choose Only select repositories, set an expiration, and grant the permissions in the table below. Click Generate token and copy it (it starts with github_pat_).

3. Save it in AWFlow. Open Credentials and click Add Credential (or + Add Credential in a node’s Credential field), then fill the New Credential form. In the browser side panel the form comes in two steps: tap GitHub in the list, then fill the rest.

   12345

   1. 1 Étape 1 : Pick GitHub Under Integration App / Service, pick GitHub. There is no Auth Type menu: GitHub uses a Bearer Token.
   2. 2 Étape 2 : Name it For example GitHub – my repos. A Description is optional.
   3. 3 Étape 3 : Paste the token Paste the token into Bearer Token.
   4. 4 Étape 4 : Check where it is saved Signed in, choose Local (this browser only) or Cloud (synced to your account) under Storage location. Without an account it is saved locally in this browser, as here.
   5. 5 Étape 5 : Click Create Credential Vérification : the credential is listed on the Credentials page, ready to pick in nodes.

   Zones numérotées de la capture d'écran : 1. Integration App / Service: GitHub; 2. Name; 3. Bearer Token; 4. Where the secret is stored (here, locally in this browser); 5. Create Credential.

Check it's connected — 

Run Repository › List in a GitHub node: the repositories the token can see come back.

Classic token

1. Create the token under Personal access tokens › Tokens (classic), with the repo scope (or public_repo for public repositories only). Copy it (it starts with ghp_).

2. Save it in AWFlow. Open Credentials and click Add Credential (or + Add Credential in a node’s Credential field), then fill the New Credential form. In the browser side panel the form comes in two steps: tap GitHub in the list, then fill the rest.

   12345

   1. 1 Étape 1 : Pick GitHub Under Integration App / Service, pick GitHub. There is no Auth Type menu: GitHub uses a Bearer Token.
   2. 2 Étape 2 : Name it For example GitHub – classic. A Description is optional.
   3. 3 Étape 3 : Paste the token Paste the token into Bearer Token.
   4. 4 Étape 4 : Check where it is saved Signed in, choose Local (this browser only) or Cloud (synced to your account) under Storage location. Without an account it is saved locally in this browser, as here.
   5. 5 Étape 5 : Click Create Credential Vérification : the credential is listed on the Credentials page, ready to pick in nodes.

   Zones numérotées de la capture d'écran : 1. Integration App / Service: GitHub; 2. Name; 3. Bearer Token; 4. Where the secret is stored (here, locally in this browser); 5. Create Credential.

Check it's connected — 

Run Repository › List: your repositories come back.

Where your token lives

Where your token lives — 

The credential is stored where you choose when you create it:

• Local (this browser only): encrypted in this browser. The encryption key is kept on the same device, so turn on the local secret vault to lock it with a passphrase only you know.
• Cloud (synced to your account): sent over an encrypted connection and stored encrypted on AWFlow’s server, so it works on your other devices.

When a step runs, your browser sends it only to api.github.com. AWFlow’s servers never relay the call.

Privacy & your data →

Permissions each operation needs

Operation	Fine-grained permission
Issue · Get, List	Issues: Read
Issue · Create, Update, Comment, Close	Issues: Read and write
Pull request · Get, List, List files	Pull requests: Read
Pull request · Review	Pull requests: Read and write
Pull request · Comment	Pull requests: Read and write (or Issues: Read and write)
Release · Get latest, List	Contents: Read
Repository · Get, List	Metadata: Read (always included)
Repository · Search	None: searches public repositories

Common issues

• “Bad credentials”. The token is wrong, expired or revoked. Generate a new one and update the credential.
• “Not Found” on a repository you can see. The token doesn’t include that repository, or lacks the permission. Edit the token on GitHub.
• “Resource not accessible by personal access token”. The organization requires approval for fine-grained tokens, or the permission is missing.
• “API rate limit exceeded”. Too many requests in the last hour. Wait, or run the workflow less often.

Related

GitHub node

All connections

Create and manage credentials

Privacy & your data