Integration · Developer
AI agents for Sentry
List, read, resolve and ignore error issues in a sentry.io organization, in its US or EU (Germany) data region.
- Actions
- 3
- Read
- 2
- Write
- 1
Actions
What your agents can do in Sentry
List, read, resolve and ignore error issues in a sentry.io organization, in its US or EU (Germany) data region. Self-hosted Sentry is not supported.
Read 2
Look things up. Nothing changes.
List unresolved issues
Lists a project's issues, most recently seen first, as result: each with its ID, short ID, title, culprit, level, status, event count, user count, first and last seen, and web address.
Get an issue
Reads one issue by its numeric ID: title, culprit, level, status, event and user counts, first and last seen, assignee and web address.
Write 1
Create, change or send.
Resolve or ignore an issue
Changes an issue's status: resolved, resolvedInNextRelease (resolved once the next release ships), ignored (archived, optionally for a number of minutes), or unresolved to reopen it.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Sentry account.
What you enter
- Auth token
Settings
- Organization slug
- Data region
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Sentry data
Ask a question in plain words. The agent can list unresolved issues or get an issue in Sentry, then answers with what it found.
- 02
Let an agent update Sentry
Have the agent resolve or ignore an issue in Sentry as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Sentry and Slack: it can list unresolved issues in Sentry and post a summary to a Slack channel in the same run.
Works well with
More Developer tools
- GitHub4 actionsOpen and comment on issues, and start GitHub Actions workflows, in the repositories a personal access token can reach.
- GitLab4 actionsOpen and comment on issues, and start CI/CD pipelines, in the GitLab.com projects an access token can reach.
- Bitbucket3 actionsComment on and read pull requests, and start Bitbucket Pipelines, in the Bitbucket Cloud repositories your Atlassian API token can reach.
- Datadog2 actionsPost events to the Datadog Event Explorer and send custom metric points, on any Datadog site, with an API key.
- PagerDuty4 actionsOpen, acknowledge and resolve PagerDuty incidents, add notes to them, and see who is on call for a schedule.
- App Store Connect8 actionsLook after iPhone, iPad and Mac apps on Apple's App Store.
FAQ
Sentry and MyDeepAgents
Can MyDeepAgents connect to Sentry?
Yes. The Sentry connector has 3 actions: 2 read and 1 makes changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Sentry?
Paste an API key from your Sentry account. You'll need: Auth token. The connection also asks for: Organization slug and Data region. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Sentry without asking?
Only if you let it. Its one action that changes data can be set to wait for a person's approval before it runs.
Can I use Sentry in workflows as well as agents?
Yes. Every Sentry action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Sentry to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.