GitHub Actions "Resource not accessible by integration"

By Kaveh Alemi·Latchkey

The GITHUB_TOKEN tried an API call it is not scoped for. This is a permissions problem, not a transient one, so retrying the job will not fix it.

What this error means

A step using the GITHUB_TOKEN fails with HTTP 403 "Resource not accessible by integration", typically when commenting, labeling, or creating a release.

RequestError [HttpError]: Resource not accessible by integration
  status: 403

Common causes

Missing scope in permissions

The default token is read-only or lacks the specific scope (issues, pull-requests, contents) the call needs.

Org default token restricted

The organization sets the default GITHUB_TOKEN to read-only, so writes fail until granted explicitly.

How to fix it

Grant the exact scope needed

1. Add a permissions block granting the required write scope.
2. Scope it to the job that needs it for least privilege.

permissions:
  issues: write
  pull-requests: write

How to prevent it

• Declare explicit least-privilege permissions on every workflow.
• Map each API call to its required GITHUB_TOKEN scope.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions