Skip to main content

Connect GitHub

Quick start​

Connect GitHub in NEXT, install the NEXT GitHub App on the repositories you want to use, and then build an automation that reacts when a new GitHub issue is opened. The same connection can also be used by automation actions that post comments back to GitHub issues.

If you need help building the automation itself, see Set up automation.

Why connect GitHub?​

GitHub is often where product feedback becomes actionable engineering work. Connecting GitHub to NEXT lets teams use new issues as an automation trigger so product, support, and engineering workflows can react immediately when a repository receives fresh input.

  • It turns newly opened GitHub issues into automation-ready events in NEXT.
  • It keeps follow-up workflows tied to the original repository and issue.
  • It allows NEXT automations to post comments back into GitHub issues when you want to acknowledge, route, or enrich them.

What the integration does​

This integration is an automation connection, not an import.

  • Trigger into NEXT: a new GitHub issue is opened.
  • Write-back from NEXT: automations can create a comment on a GitHub issue.

What it does not do​

  • It does not import your existing GitHub issues into NEXT as Highlights or Recordings.
  • It does not sync closed issues, edited issues, pull requests, or repository history.
  • It only reacts to newly opened issues received through the GitHub webhook.

How connection works​

  1. In NEXT, open Settings -> Integrations -> GitHub.
  2. Click Connect.
  3. GitHub opens the NEXT GitHub App installation flow.
  4. Choose the GitHub user or organization that should own the installation.
  5. Select the repositories you want the NEXT app to access.
  6. Complete the install or update flow in GitHub.
  7. Return to NEXT and use the connected GitHub integration in your automation.

NEXT stores the GitHub App installation ID for the connection. That installation ID is what NEXT uses both for incoming webhook events and for posting comments back to GitHub later.

Repository and connection limits​

How many GitHub integrations can a Teamspace have?​

One Teamspace should use one GitHub installation connection.

That single connection can cover multiple repositories, as long as those repositories are included in the same GitHub App installation.

Can the same GitHub installation be connected to more than one Teamspace?​

Yes. The same GitHub App installation can be connected in more than one Teamspace when those Teamspaces need to use the same GitHub repositories for automation workflows.

Configuration notes​

  • Repository access is controlled from the GitHub App installation, not from NEXT.
  • If you add or remove repositories in GitHub, that changes which repositories can trigger automations through this connection.
  • Only issues opened after the webhook is active can trigger NEXT automations.

Troubleshooting​

GitHub says the repository is already installed, but NEXT still shows "not connected"​

Most often, the GitHub App installation is still present, but the connection flow did not finish cleanly in NEXT or the selected repository is not available through the installed GitHub App scope.

Check these points:

  • Confirm that you completed the GitHub install/update flow and returned to NEXT successfully.
  • Confirm that the repository is included in the selected GitHub App installation.

If you want to connect the same GitHub installation to another Teamspace, GitHub currently only redirects back to NEXT when the installation is actually updated, for example by adding or removing repository access. In practice, this means you may need to change the selected repositories during the GitHub update flow before GitHub sends you back to NEXT.

This is a known limitation of GitHub's installation flow. NEXT relies on that redirect so it can verify the installation details coming back from GitHub instead of trusting unverified repository access claims.

I cannot uninstall or reset NEXT from the GitHub side​

If GitHub no longer shows NEXT as an installed app, but NEXT still has an existing GitHub connection recorded, the GitHub-side state and NEXT-side state may be out of sync. In that case, check the existing GitHub integration in NEXT first before trying to reconnect.

My automation does not fire​

Check the following:

  • The GitHub issue was newly opened after the integration was connected.
  • The repository is part of the installed GitHub App scope.
  • Your automation is configured to react to the GitHub issue trigger.
  • The issue event is an issue creation event, not a pull request or another repository activity.

NEXT cannot post a GitHub comment​

Make sure the Teamspace still has the correct GitHub connection and that the GitHub App installation still has access to the target repository. Comment actions use the stored installation ID from the connected integration.

FAQ​

Does GitHub import issues into NEXT?​

No. This integration currently works as an automation trigger and comment action, not as a historical issue import.

Can I connect more than one repository?​

Yes. A single GitHub connection can cover multiple repositories if they are selected in the same GitHub App installation.

Can I connect the same GitHub account or organization to multiple Teamspaces?​

Yes. If multiple Teamspaces need to use the same GitHub App installation, each Teamspace can connect GitHub separately.

Which GitHub events trigger NEXT?​

This integration currently reacts to newly opened issues.

Can NEXT write back to GitHub?​

Yes. Automations can post comments to GitHub issues by using the connected GitHub installation.