Skip to main content
Integrations · Sentry
Guild agents list and inspect Sentry issues, read the events and stack traces behind them, and check releases and monitors through the Sentry REST API. Guild stores your Sentry token and injects it server-side, so agent code never sees it. Credential policies decide which Sentry operations each agent may call.

Book a demo

See how teams govern agents that use Sentry.

Talk to sales

Get access to Guild, then connect Sentry to your first agent.

What the Sentry integration exposes

The integration is guildai~sentry. Tools cover issues and their events, projects, releases, organizations, teams, members, cron monitors, replays, environments, dashboards, Discover queries, and integrations. Requests go to https://sentry.io. The set isn’t read-only. It includes tools that update issues, change project settings, and permanently remove issues, such as sentry_bulk_remove_a_list_of_issues.

How it works

1

Create a Sentry token

In Sentry, open User settings > Personal tokens and create a token with the scopes your agent needs, such as event:read, project:read, and org:read for triage.
2

Connect the token in Guild

Go to Access & setup > Credentials, click Connect, select sentry, and paste the token into API Key.
3

Import the tools you need

Import SentryTools from @guildai-services/guildai~sentry and use pick() to give the agent only the tools its job needs.

Why Sentry access needs governing

The same integration that reads a stack trace can delete a project. Two controls narrow it. Grant the Sentry token only the scopes the agent needs, and write credential policies that Guild checks before any request reaches Sentry. A triage agent can read issues and events while a DENY rule blocks every delete and remove tool.

Authentication

  • Type: API key
  • Header: Guild sends the token as Authorization: Bearer <token>
  • Token: a Sentry personal token, limited to the scopes you grant
See Credentials for workspace, member, and agent-scoped credentials.

Usage

Tools are named with the sentry_ prefix. The integration has more than 200 tools, so pick the ones the agent needs rather than spreading the whole set.

Tools

Tools in the latest published version of guildai~sentry:

Frequently asked questions

No. Requests go to https://sentry.io, and the address is fixed when the integration is published. For a self-hosted instance, create a custom integration with your own base URL.
Not yet. Guild doesn’t receive Sentry alerts, so you can’t create an event trigger for Sentry. Run the agent on a schedule instead.
Yes, in two layers. Leave admin and write scopes off the token, and write a credential policy that denies delete and remove operations. See Credential policies.
Also runs on Guild: Datadog · New Relic · Splunk Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 4, 2026