Before you begin
Make sure you have:- A Potpie account
- A Sentry account with permission to authorize OAuth applications on your organization
The same Sentry organization cannot be connected more than once per user. If you attempt to reconnect an already-linked organization, Potpie will return a duplicate error. Delete the existing integration first.
Connect your Sentry account
Open Integrations
Go to Potpie → Integrations.
What Sentry data becomes accessible
Unlike the Jira and Confluence integrations, Sentry does not expose agent-callable tools. Instead, connecting Sentry makes your organization’s data available to the service layer — projects, issues, and events can be retrieved and used as context in conversations. The following data endpoints become active once you connect:Lists all Sentry organizations accessible to the connected account.
Lists all projects within a specific organization.
Returns issues for a specific project. Use this to retrieve error context for conversations about a codebase.
Generic passthrough to any Sentry API endpoint. All requests go through Potpie’s token layer, so your credentials are never exposed directly.
Token refresh
Potpie automatically refreshes your Sentry access token when it expires. No action is required from you — data access continues without interruption across token cycles.Webhooks
Sentry can push issue and project events to Potpie in real time. A few things to know:- Registration is manual — Potpie does not register webhooks automatically at connection time. You need to add the webhook URL on Sentry’s side yourself.
- All event types are accepted — Potpie does not filter by event type. Any event Sentry sends is received and queued for processing.
- Webhook endpoint:

