Skip to main content

​
Overview

Friday can fetch pull requests, track repository activity, retrieve commit history, and generate release notes from your GitHub repositories. To enable these capabilities you must provide a GitHub Personal Access Token (PAT). This is a one‑time setup; after it’s configured Friday will use GitHub automatically whenever a task requires it.

​
Prerequisites

  1. A GitHub account with access to the repositories you want Friday to interact with.
  2. Permission to create Personal Access Tokens (available to all GitHub users).
  3. For private repositories, you must generate a token with the appropriate scopes. Public repositories work without a token.

​
Step‑by‑Step Guide

Friday will automatically detect when you need to connect to GitHub as part of your regular use.
1

Start with a real GitHub request

Tell Friday what you want to do with GitHub. This gives Friday the context it needs to request your Personal Access Token.Example prompts:
  • “List all open pull requests in the myorg/frontend repository.”
  • “Show me the commit history for the main branch in myorg/api from the last week.”
  • “Generate release notes from all merged PRs in myorg/backend since the last release.”
  • “Every Friday at 3pm PT, summarize this week’s merged pull requests and post them to Slack.”
2

Connect GitHub

​
Start the token setup flow

If you haven’t connected GitHub previously, Friday will automatically detect that you need to provide a Personal Access Token.
  • Click Connect GitHub.
  • You’ll see a field to paste your GitHub Personal Access Token.
3

Create a GitHub Personal Access Token

To generate a token:
  1. Go to GitHub Settings → Developer Settings → Personal Access Tokens
  2. Choose your token type:
    • Fine‑grained tokens (recommended): Click “Generate new token” under Fine‑grained tokens
    • Classic tokens: Click “Generate new token (classic)”
  3. Configure your token:
    • Give it a descriptive name (e.g., “Friday Integration”)
    • Set an expiration date (shorter is more secure; you can regenerate when it expires)
    • Select the scopes/permissions needed:
      • For read‑only access (fetch PRs, commits, releases): repo:status, public_repo (classic) or Read access to code and metadata (fine‑grained)
      • For write access (create issues, comment on PRs): Add repo (classic) or Read and write access to code, issues, and pull requests (fine‑grained)
    • For fine‑grained tokens, select the specific repositories Friday should access
  4. Click “Generate token” and copy the token immediately (you won’t see it again)
4

Paste the token into Friday

  • Return to Friday and you’ll see two fields:
    • Label: Give this connection a descriptive name (e.g., “My GitHub Account” or “Work GitHub”)
    • API Key: Paste your GitHub Personal Access Token here
  • Click Connect.
  • Friday will confirm that the connection succeeded.
5

Continue your task

After you provide the token, the task you set up in Step 1 will continue automatically, and Friday will now be able to interact with your GitHub repositories.
6

Use GitHub for future automations

Whenever you need GitHub in a task simply include the GitHub action in your prompt. Because the token is now configured, Friday will handle the operation automatically; no further credential steps are required.

​
Security & Permissions

  • Friday stores your Personal Access Token securely; the raw token is never exposed in the UI.
  • The token is scoped only to the permissions you selected when creating it.
  • For fine‑grained tokens, you can restrict access to specific repositories.
  • Revoking or expiring the token in GitHub automatically disables Friday’s access; you’ll need to generate and provide a new token to restore functionality.

​
Revoking Access

Note: By revoking access, any current and future workspaces set up with Friday will no longer be able to use GitHub until you provide a new token.

​
To revoke a Personal Access Token:

  1. Go to GitHub Settings → Developer Settings → Personal Access Tokens
  2. Find the token you created for Friday (e.g., “Friday Integration”)
  3. Click Delete or Revoke

​
To update an expired token:

  1. Generate a new token following the steps in Step 3 above
  2. In Friday, go to Settings → Integrations
  3. Find GitHub and click Update token
  4. Paste the new token and save