Skip to main content

​
How it works

Connect your Zite app to GitHub to read repository contents, manage issues and pull requests, and respond to repository updates. App visitors don’t need to connect their own GitHub accounts. Depending on the access you grant, your app can:
  • List and access repositories available to the connection
  • Read file contents from repositories
  • Create and manage issues
  • Open pull requests and track commits
  • Monitor GitHub Actions workflow runs
  • Receive webhook notifications for repository events
Important: The GitHub integration uses the identity of the person who connects the account. All actions are performed as that user, not as individual app visitors.

​
How to integrate GitHub into your app

1

Connect to GitHub

In the chat box, request your app to be integrated with GitHub. Alternatively, click + in the chat box, select Integrations, then choose GitHub.You can connect using one of two methods:Option 1: Sign in with GitHub (recommended)Sign in to your GitHub account and approve Zite’s request to access your repositories and profile. Your organization’s settings may require an administrator’s approval or an extra sign-in step before Zite can access its repositories.Option 2: Personal access tokenTo choose exactly which repositories Zite can access, create a fine-grained personal access token in GitHub. A token is a private key that gives Zite permission to work with your GitHub account. Select the repositories and allow the actions your app needs, such as reading files or creating issues and pull requests. Your organization may need to approve the token before it works.In Zite, click Use a personal access token, paste your token, then click Connect with token. Existing classic personal access tokens are also supported. If your organization uses single sign-on (SSO), follow GitHub’s prompts to authorize the token for that organization.Once connected, your app can perform the actions allowed by both your GitHub account and the connection’s permissions.
2

Enter use case

Tell Zite how you want to use GitHub in your app. For example, “Create an issue tracker that lets users create GitHub issues” or “Build a repository browser that shows file contents.”
3

Test and publish

Test your integration using the chat box or the respective buttons in your app to ensure everything’s working properly.Click Publish in the upper right corner to deploy your changes and make the GitHub integration available in your live app.

​
Common use cases

With a GitHub connection, you can create apps like:
  • Issue Management Tools: Let users create and track GitHub issues with custom labels and assignees
  • Repository Browsers: Display repository contents and file viewers for your team
  • Pull Request Dashboards: Monitor open pull requests and their status across repositories
  • CI/CD Monitors: Track GitHub Actions workflow runs and build status
  • Commit Trackers: Show recent commits on specific branches with author and timing information
  • Webhook Receivers: Build apps that respond to GitHub events like pushes, pull requests, or issue updates

​
Important notes and limitations

Usage limits: GitHub usually allows 5,000 requests per hour for the connected account. Your app shares this allowance with other apps and tools using that account. GitHub may also temporarily limit requests made too quickly. If you reach a limit, wait before trying again and ask Zite to reduce how often your app checks GitHub. Connected account: Everyone using your app interacts with GitHub through the account you connected. Choose your app’s audience and available actions with that account’s access in mind. Connection problems:
  • If GitHub rejects the connection (401), reconnect your account or replace your token. The token may be invalid, expired, or revoked.
  • If an action is blocked (403), check the connection’s permissions and your organization’s approval requirements. This can also happen when you reach a usage limit.
  • If GitHub reports too many requests (429), wait before trying again.
  • If a private repository appears to be missing (404), check that both your account and the connection have access to it.
Repository notifications: Your app can receive webhooks—automatic notifications about GitHub activity. Zite protects the receiving address with a private token, but it cannot verify GitHub’s signature to confirm who sent a notification. Avoid using these notifications alone to approve destructive actions, such as deleting data. GitHub Actions: Your app can monitor workflow runs with the appropriate repository access. Changing the workflow files themselves requires additional permission. The standard GitHub sign-in connection doesn’t include this access. For a personal access token, enable the workflow scope on a classic token, or Workflows: write along with the required file permissions on a fine-grained token. Token security: Zite makes the GitHub token available to your app on the server. Keep it private and never include it in content shown to app visitors.
Need help with your GitHub integration? Contact us at support@zite.com
Last modified on September 17, 2026