> ## Documentation Index > Fetch the complete documentation index at: https://docs.stackone.com/llms.txt > Use this file to discover all available pages before exploring further. # GitHub Webhook Setup Guide > Configure GitHub to deliver events to StackOne. ## Prerequisites The connector should already be set up, with a Connector Profile and a Linked Account. See [Getting Started](/connectors/github#getting-started) on the GitHub connector page.
Select Actions to adjust the guide
Some actions may require additional configuration in the provider to be accessible. Choose the actions you need and the guide will be updated.
Action
Scope(s)
Loading actions...
Dynamic Guide URL
Scopes Selected

          

            
Separator

Setting Up Webhooks with a GitHub App

Follow these steps if you connected your account with a GitHub App and wish to receive real-time event notifications. Webhooks are registered per repository or per organisation, and each linked StackOne account has its own Native Webhook URL.

If you connected with a Personal Access Token instead, follow the next section.

Sign in to your GitHub account, or to your own instance on GitHub Enterprise Server, and navigate to developer settings.

  • Click your profile photo in the upper-right corner
  • Select Settings from the dropdown
  • In the left sidebar, scroll down and click Developer settings
  • Create a GitHub App if you have not already done so (see the previous section), or open your existing app by clicking its name under GitHub Apps in the left sidebar

After linking your account in StackOne, a Native Webhook URL is generated for that linked account.

  • Open Linked Accounts in StackOne and click Edit on your GitHub account
  • Copy the Native Webhook URL from the Configuration form
  • Note: The URL is unique to this linked account. Do not reuse it for another account.

Add the URL you copied to each GitHub repository or organisation you wish to receive events from.

  • Scroll to the Webhooks section of your GitHub repository or organisation settings
  • Paste the copied Native Webhook URL into the Webhook URL field
  • Leave the Secret field empty
  • Keep Enable SSL verification selected
  • Select Active to enable the webhook
  • Click Save Changes to save the webhook
GitHub App developer settings webhook form
Enables actions: Add Collaborator, Add Team Member, Add Team Repository, Cancel Workflow Run, Check Organization Membership, Create Deployment, Create Deployment Status, Create Git Reference, Create Issue, Create Issue Comment, Create Or Update File, Create Organization Repository, Create Pull Request, Create Pull Request Review, Create Pull Request Review Comment, Create Release, Create Team, Create User Repository, Create Webhook, Delete Deployment, Delete File, Delete Git Reference, Delete Release, Delete Repository, Delete Team, Delete Webhook, Download Artifact, Fork Repository, Get Authenticated User, Get Branch, Get Branch Rules, Get Combined Status For Ref, Get Commit, Get Git Reference, Get Issue, Get Latest Release, Get Organization, Get Organization Membership, Get Pull Request, Get Repository, Get Repository Content, Get Repository Ruleset, Get Team, Get Unified Credentials, Get Unified Group, Get Unified Organization, Get Unified Role, Get User, Get Webhook, Get Workflow Run, Invite Organization Member, List Artifacts, List Authenticated User Organizations, List Authenticated User Repositories, List Branches, List Check Runs For Ref, List Code Scanning Alerts, List Collaborators, List Commits, List Dependabot Alerts, List Deployments, List Forks, List Issue Comments, List Issues, List Matching Git References, List Organization Branch Protection, List Organization Members, List Organization Members With Two-Factor Status, List Organization Repositories, List Outside Collaborators, List Pull Request Reviews, List Pull Requests, List Pull Requests For Commit, List Releases, List Repository Rulesets, List Secret Scanning Alerts, List Team Members, List Team Repositories, List Teams, List Unified Groups, List Unified Organizations, List Unified Roles, List Unified Users, List User Organizations, List User Repositories, List Users, List Webhooks, List Workflow Jobs, List Workflow Runs, Merge Pull Request, Ping Webhook, Re-run Workflow, Remove Collaborator, Remove Organization Member, Remove Team Member, Search Code, Search Issues, Search Pull Requests With Reviews, Search Repositories, Star Repository, Trigger Workflow, Unstar Repository, Update Code Scanning Alert, Update Dependabot Alert, Update Git Reference, Update Issue, Update Pull Request, Update Release, Update Repository, Update Secret Scanning Alert, Update Team, Update User, Update Webhook, Upload Release Asset

Set the permissions your integration requires. GitHub Apps use fine-grained permissions rather than traditional OAuth scopes.

Important: these permissions are set in the GitHub App configuration and cannot be changed during authorisation. Users see these permissions when they authorise the app, and can choose which repositories to grant access to.

  • Select Permissions & events in the left sidebar
  • Under Subscribe to events, select the events you wish to receive:
  • - Code scanning alert: Code Scanning alert updated. This event is triggered when the assignees or state of the alert changes. The state can be created, fixed in branch, or closed.
  • - Check run: Check run is created, requested, rerequested, or completed.
  • - Check suite: Check suite is requested, rerequested, or completed.
  • - Create: Branch or tag created.
  • - Delete: Branch or tag deleted.
  • - Dependabot alert: Dependabot alert assignees\_changed, auto\_dismissed, auto\_reopened, created, dismissed, reopened, fixed, or reintroduced.
  • - Deployment: Repository was deployed or a deployment was deleted.
  • - Deployment status: Deployment status updated from the API.
  • - Fork: Repository forked.
  • - Issues: Issue opened, edited, deleted, transferred, pinned, unpinned, closed, reopened, assigned, unassigned, labeled, unlabeled, milestoned, demilestoned, locked, unlocked, typed, untyped, field\_added, or field\_removed.
  • - Issue comment: Issue comment created, edited, or deleted.
  • - Member: Collaborator added to, removed from, or has changed permissions for a repository.
  • - Organization: Organization deleted, renamed, member invited, member added, or member removed.
  • - Pull request: Pull request assigned, auto merge disabled, auto merge enabled, closed, converted to draft, demilestoned, dequeued, edited, enqueued, labeled, locked, milestoned, opened, ready for review, reopened, review request removed, review requested, synchronized, unassigned, unlabeled, or unlocked.
  • - Pull request review: Pull request review submitted, edited, or dismissed.
  • - Pull request review comment: Pull request diff comment created, edited, or deleted.
  • - Push: Git push to a repository.
  • - Release: Release created, edited, published, unpublished, or deleted.
  • - Repository: Repository created, deleted, archived, unarchived, publicized, privatized, edited, renamed, or transferred.
  • - Secret scanning alert: Secret scanning alert created, resolved, reopened, validated, publicly leaked, assigned, or unassigned.
  • - Star: A star is created or deleted from a repository.
  • - Team: Team is created, deleted, edited, or added to/removed from a repository.
  • - Workflow job: Workflow job queued, waiting, in progress, or completed on a repository.
  • - Workflow run: Workflow run requested or completed on a repository.
  • Click Save changes at the bottom of the page
GitHub App event subscriptions

After updating permissions or events, reinstall the app to apply the new configuration. Existing installations do not pick up changes to permissions or subscribed events automatically.

  • Select the Install App tab in the left sidebar
  • Click the Configure icon next to your existing installation
  • You are taken to the installation page for the account or organisation where the app is installed
  • Click Authorize to apply the new permissions and event settings, or accept the updated permissions if you are prompted to review them
  • If you are not prompted, uninstall the app and install it again
  • After reinstalling, return to StackOne and click Edit on the linked account to reauthorise the connection

Setting Up Webhooks with a Personal Access Token

Follow these steps if you connected your account with a Personal Access Token. The webhook is registered directly on the repository or organisation, and each linked StackOne account has its own Native Webhook URL.

After linking your account in StackOne, a Native Webhook URL is generated for that linked account.

  • Open Linked Accounts in StackOne and click Edit on your GitHub account
  • Copy the Native Webhook URL from the Configuration form
  • Note: The URL is unique to this linked account. Do not reuse it for another account.

Navigate to the webhook settings of the repository or organisation you wish to receive events from.

  • Open the repository in your organisation on GitHub
  • Click the Settings tab
  • In the left sidebar, under Code, planning, and automation, click Webhooks
  • Click Add webhook

Point the webhook at StackOne and send the payload as JSON.

  • Paste the copied Native Webhook URL into the Payload URL field
  • Set Content type to application/json
  • Leave the Secret field empty
  • Keep Enable SSL verification selected

Under Which events would you like to trigger this webhook?, choose Let me select individual events, then select the events you wish to receive.

  • - Branch or tag creation: Branch or tag created.
  • - Branch or tag deletion: Branch or tag deleted.
  • - Check runs: Check run is created, requested, rerequested, or completed.
  • - Check suites: Check suite is requested, rerequested, or completed.
  • - Code scanning alerts: Code scanning alert updated. Triggered when the assignees or state of the alert changes. The state can be created, fixed in branch, or closed.
  • - Commit comments: Commit or diff commented on.
  • - Dependabot alerts: Dependabot alert assignees changed, auto dismissed, auto reopened, created, dismissed, reopened, fixed, or reintroduced.
  • - Deployment statuses: Deployment status updated from the API.
  • - Deployments: Repository was deployed or a deployment was deleted.
  • - Forks: Repository forked.
  • - Issue comments: Issue comment created, edited, or deleted.
  • - Issues: Issue opened, edited, deleted, transferred, pinned, unpinned, closed, reopened, assigned, unassigned, labeled, unlabeled, milestoned, demilestoned, locked, unlocked, typed, untyped, field added, or field removed.
  • - Pull request review comments: Pull request diff comment created, edited, or deleted.
  • - Pull request reviews: Pull request review submitted, edited, or dismissed.
  • - Pull requests: Pull request assigned, auto merge disabled, auto merge enabled, closed, converted to draft, demilestoned, dequeued, edited, enqueued, labeled, locked, milestoned, opened, ready for review, reopened, review request removed, review requested, stacked, synchronized, unassigned, unlabeled, or unlocked.
  • - Pushes: Git push to a repository.
  • - Releases: Release created, edited, published, unpublished, or deleted.
  • - Repositories: Repository created, deleted, archived, unarchived, publicized, privatized, edited, renamed, or transferred.
  • - Secret scanning alerts: Secret scanning alert created, resolved, reopened, validated, publicly leaked, assigned, or unassigned.
  • - Stars: A star is created or deleted from a repository.
  • - Statuses: Commit status updated from the API.
  • - Team adds: Team added or modified on a repository.
  • - Workflow jobs: Workflow job queued, waiting, in progress, or completed on a repository.
  • - Workflow runs: Workflow run requested or completed on a repository.
GitHub repository webhook form

Save the webhook to begin receiving events.

  • Select Active to enable the webhook
  • Click Add webhook
  • Reconnect the account in StackOne so the new configuration is applied
## Verify Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.