> ## Documentation Index
> Fetch the complete documentation index at: https://docs.usecustory.com/llms.txt
> Use this file to discover all available pages before exploring further.

# GitHub integration

> Connect GitHub repositories, issues, pull requests, webhooks, and PR-comment AI.

Use this page as a reference for the GitHub integration.

## Capability table

| Field                | Value                                                                                                                     |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Status               | Available                                                                                                                 |
| Connection method    | GitHub App installation and OAuth authorization                                                                           |
| Custory reads        | Selected repositories, issues, pull requests, repository metadata, README content, PR comments, and webhook events        |
| Custory writes       | GitHub issues, issue updates/comments, repository webhooks, and PR comments from Custory AI                               |
| Automation support   | PR opened, PR merged, and PR comment mention events                                                                       |
| Required permissions | Access to the selected repositories, plus permission to read PRs and issues and create webhooks on those repositories     |
| Known limitations    | Custory only works on the repositories you connect or select. GitHub-triggered workflows require at least one repository. |

## What it does

* Create a GitHub issue from a journey item
* Keep journey defaults pointed at the right repository
* Follow pull request activity in the journey
* Trigger automations when a PR opens or merges
* Use Custory AI in a PR comment thread on a connected repository

## How to set it up

1. Open **Manage Integrations** and connect GitHub.
2. Select the repositories Custory should use.
3. Set journey defaults if one journey always routes work to the same repo.
4. Create a linked issue from a journey item to check the handoff.
5. Turn on PR-based automations if you want delivery events to trigger follow-up.

## How Custory uses GitHub

Custory can read:

* repository listings
* issue lists and issue details
* pull request lists and pull request details
* repository metadata and README content for AI context
* webhooks for `issue_comment` and `pull_request` events

Custory can write:

* GitHub issues
* issue updates or comments
* repository webhooks
* PR comments from Custory AI

## PR-comment AI

When a connected repository sends PR comment events, mentioning Custory AI in the thread can start an async response in that PR. Custory uses the PR title, description, recent comments, and matching journey context from the connected repository, then posts the result back to GitHub.

## Limits

* Custory only works on selected repositories, not every repository in the account.
* GitHub-triggered automations need at least one connected repository.
* Journey defaults reduce routing friction, but they do not replace choosing the right repo.
* If the integration is expired or disconnected, GitHub actions will stop until you reconnect it.

## Related pages

* [External tasks and issues](/external-tasks)
* [Automations](/automations)
* [Integrations](/integrations)