Sentry: what this connector can do

Member·4 minutes to read

What this page is for

docs/connectors/sentry.md is the setup guide for whoever runs your organisation's Botseon deployment — creating the organization auth token Sentry needs and entering it. This page is the other half: what Sentry actually lets a bot do once that token is connected, what it asks you for along the way, its limits, and how to take the connection away again, in Botseon and at Sentry.

List projects and issues, and read an issue's events and organization-wide stats.

What a bot can do with it

Read — Sentry tells a bot things, nothing changes

Tool	What it does
`sentry.list_projects`	List the projects in the organization.
`sentry.list_issues`	List issues in a project, filtered by search query and status.
`sentry.get_issue`	Read one issue by id, including its status and counts.
`sentry.list_events`	List the events recorded for one issue.
`sentry.get_org_stats`	Read organization-wide event volume statistics.

Write

This connector has no write tools yet. A bot can only read through it.

The permissions it asks for, in plain words

Every call a bot makes through this connector is tagged with what kind of thing it is. Only the tags below ever apply here — a tag this connector's tools never carry is not listed, because it can never ask you for it.

read — Looks something up. Nothing changes, and nothing is sent anywhere. A bot never has to ask first for this.

Limits

List projects and issues, and read an issue's events and organization-wide stats. Nothing outside that list is possible through this connector, however a bot is asked to use it.

Sentry is also only ever as wide as the organization auth token your deployment actually holds — the exact checklist is on the operator's own setup page, docs/connectors/sentry.md, because choosing it is a decision for whoever runs your deployment, not for this page.

Disconnecting

In Botseon

Open Plugins from the sidebar, press this connector's card to open its detail page, and under Accounts press the ✕ next to the account (its label is "Remove account" and the name of the account), then Revoke and remove to confirm — or Uninstall to remove the plugin and every account connected to it at once. Either one revokes the stored connection immediately: nothing more is read or changed through it from that moment on. Install a plugin walks through the same screen step by step.

At Sentry

Removing the account in Botseon deletes the stored token from Botseon, but the token itself stays valid at Sentry until you delete or rotate it yourself. Do that from Sentry's own Settings → Auth Tokens page — the same place it was created — which is the only way to be sure nothing else can use it, since Botseon has no way to revoke a token it did not issue.

What Botseon keeps, and how your data is used

Whatever a bot reads or writes through this connector becomes part of your conversations and the record of that run — the same records, and the same retention schedule, as everything else a bot works on. Botseon is the processor for that content; your organisation decides what it may read and remember, and can delete it sooner than the schedule would on its own.

Your data is sent to a model provider only to produce the bot's answer, and for nothing else — it is not used to train any model. The Privacy Policy's Models and How long we keep it sections have the full detail, including exactly how long each kind of record is kept for.