Developer Tools · Integration
GitHub
Add GitHub to your product for your customers, and give your AI agents governed access to it.
GitHub is where engineering work is recorded, so an embedded GitHub integration lets your product read and write the repositories, issues, pull requests, checks and workflow runs a customer's team already lives in. Two things decide how it behaves. Token shape matters: a GitHub App installation token is scoped to the repositories that installation was granted and its limits are counted per installation, while a personal access token carries whatever the person carries, which is usually far more. And webhooks can redeliver, so the same push or review event may arrive twice and every handler has to be safe to run again. fastn keeps each installation's credentials, refreshes them, and follows GitHub's API and event changes.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer install your GitHub App on the repositories they choose, so your product sees those and nothing else.
Open, label and close issues from your product, and read pull request review state to show what is really blocking a merge.
React to a push, a review or a completed workflow run, treating a redelivered event as something already handled.
Read check runs and commit statuses so your product can say whether a branch is safe to ship.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent summarises the open pull requests on one repository and who has been asked to review each.
An agent files or updates an issue within the scopes that installation was granted, with the write attributed.
An agent reads a failing workflow run's logs before it suggests what broke.
Example prompt
Which pull requests on this repository have a failing check and have been waiting on review since last week?
Set up GitHub in 4 steps
- 01Enable the GitHub connector from your fastn dashboard.
- 02Have each customer authorise their own GitHub account, so calls run under their credentials rather than a shared key.
- 03Decide which repositories, issues, pull requests and workflow runs your product needs, then choose between an installation-scoped app token and a personal token, since rate limits differ.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the GitHub integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a GitHub integration without building it. Your customers connect their own GitHub account inside your product and work their services, builds and deployments there, with no per-customer code on your side.
- Handle the part that actually costs time: these systems emit a lot of webhooks, and replay after downtime has to be handled. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a GitHub update is not your on-call problem.
- One integration serves your product and your agents. The same governed GitHub connection powers in-product features and gives AI agents scoped, audited access, so you connect engineering activity to the rest of the business without wiring it twice.
Used by these teams
Compare with
GitLab
Bitbucket
Azure DevOpsOften used alongside
Tools the same teams tend to run next to GitHub, across other categories.
Slack
Snowflake
Airtable
PostgreSQLGitHub integration FAQ
How do I add a GitHub integration to my product?
Enable the GitHub connector in your fastn dashboard, then let each customer authenticate their own GitHub account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no GitHub client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own GitHub account?
Yes. Every connection is scoped to the individual customer, so each authorises their own GitHub account and only ever sees their own services, builds and deployments. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this GitHub integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent summarises the open pull requests on one repository and who has been asked to review each.
Who maintains the GitHub integration?
fastn does. When GitHub changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can I react to GitHub events in real time?
Yes, through event triggers. Events are delivered per tenant and can be replayed after an outage, so a webhook missed during downtime is not silently lost.
Can an agent open or update items in GitHub?
Yes, within scoped permissions, and every action is audited so an agent's changes are attributable.
What can I build with the GitHub integration?
A common starting point: let each customer install your GitHub App on the repositories they choose, so your product sees those and nothing else. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the GitHub integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding GitHub does not change your per-connector cost. You can start free with 3 connected accounts.
Add GitHub to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.