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

# Sentry

> Connect Sentry to your Atako agents — 9 read and 3 write actions.

Let your agents triage errors in Sentry — browse organizations, projects, teams, issues and their events, check releases and event volumes, then resolve, assign or bookmark issues and record new releases.

## Connection

* **Authentication**: API key (Sentry auth token).
* **Required settings**:
  * **Sentry host** — sentry.io for US data storage, de.sentry.io for EU data storage

<Note>
  Sentry → Settings → Custom Integrations → Create New Integration → Internal Integration → Next. Name it, set the permissions Project: Read, Team: Read, Organization: Read, Issue & Event: Read & Write and Release: Admin (only needed to create releases), Save Changes, then copy the token shown under Tokens. Alternatively, use a personal token (User settings → Personal Tokens) with the scopes org:read, project:read, team:read, event:read, event:write and project:releases. Organization tokens are not enough: they only cover CI tasks. Pick the host matching your data storage location: sentry.io (US) or de.sentry.io (EU).

  See [Sentry's documentation](https://docs.sentry.io/api/guides/create-auth-token/).
</Note>

## Read actions (9)

| Action               | Description                                                                                                                                                                                          |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `get_event_counts`   | Count the events an organization received over a period, grouped by outcome, category, reason or project (statsPeriod like "7d", or start/end).                                                      |
| `get_issue`          | Fetch one issue: status, counts, first/last seen, assignee and a summary of its latest event.                                                                                                        |
| `get_latest_event`   | Fetch the latest event of an issue with its stack trace, tags and context; llmFormat adds a compact rendering (markdown, json or xml).                                                               |
| `list_issue_events`  | List the error events of an issue over a period (statsPeriod like "24h" or "7d", or start/end in ISO-8601); full=true includes stack traces (page capped at 10).                                     |
| `list_issues`        | List the issues of a project. query is a Sentry search query (default "is:unresolved"; e.g. "is:unresolved level:error"); sort: date (last seen), new (first seen), trends, freq, user, recommended. |
| `list_organizations` | List the organizations the token can access (an internal-integration token only sees its own organization). Returns each slug, needed by every other action.                                         |
| `list_projects`      | List the projects of an organization (slug, id, platform), optionally filtered by name or slug.                                                                                                      |
| `list_releases`      | List the releases of an organization, most recent first, optionally for one project or matching a version substring.                                                                                 |
| `list_teams`         | List the teams of an organization (use "team:\<id>" as assignedTo in update\_issue).                                                                                                                 |

## Write actions (3)

| Action           | Description                                                                                                                                                                                                                                                                                                                                                    |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `create_release` | Create a release. Arguments: organization\_id\_or\_slug (string), version (string, e.g. "1.4.2" or a commit SHA), projects (array of project slug strings, at least one), ref (string, optional commit reference), url (string, optional link to the release), dateReleased (string, optional ISO-8601 date; defaults to now).                                 |
| `resolve_issue`  | Mark an issue as resolved. Arguments: organization\_id\_or\_slug (string), issue\_id (string). Nothing else.                                                                                                                                                                                                                                                   |
| `update_issue`   | Update an issue; only the fields sent change. Arguments: organization\_id\_or\_slug (string), issue\_id (string), status ("resolved" \| "unresolved" \| "ignored"), assignedTo (string: "user:\<id>", "team:\<id>", a username or a member e-mail), priority ("low" \| "medium" \| "high"), isBookmarked (boolean), hasSeen (boolean), isSubscribed (boolean). |

## Permissions

Every action above must be explicitly granted to an agent before it can be used. See [Permissions](/integrations/permissions) for the grant model and [Security](/integrations/security) for how credentials are protected.