> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/sentry.md). # Sentry Monitor Sentry issues, events, and releases. ## Connectors Choose the connector that matches your authentication method. The options below use the names shown in StackAI. | Connector | Authentication | | --------- | -------------- | | Sentry | Auth Token | ### Sentry Connect to Sentry with an organizational auth token. #### Set up in Sentry 1. Prepare the Sentry account or service that the workflow will access. Grant access to the required resources and operations. 2. Create or obtain the API credential identified in the fields below. Use the provider instructions linked with those fields to find its key-management page. #### Set up in StackAI 1. Open **Settings → Connections**, add a connection, and select **Sentry**. 2. Enter the credentials and connection details in the fields below. 3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it. **Connection fields** | StackAI field | Required | What to enter | | ------------- | ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | Auth Token | Yes | Use a Sentry organizational token with the scopes required by your actions. [Provider instructions](https://docs.sentry.io/api/guides/create-auth-token/). | | Sentry Region | Optional / as applicable | Choose the Sentry region that hosts your organization. | ### Verify the connection Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action. If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change. ## Use an action 1. Add the required **Sentry** action to the workflow. 2. Select a connection when the action requests one. 3. Complete the required fields. Use the reference picker when a value comes from another workflow step. 4. Run the workflow and inspect the action’s output. Check the result before using it in a later step. ## Actions ### List Issues Find Sentry issues that need attention. #### Inputs | Field | Type | Required | Description | | -------------- | --------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------- | | Organization | select (string) | Yes | The Sentry organization whose issues you want to search. Options load from the selected connection. | | Project | select (string) | No | Optionally limit the search to one Sentry project. Options load from the selected connection. | | Environment | string | No | Optionally limit issues to an environment. | | Search Query | string | No | A Sentry issue-search query. Default: is:unresolved. | | Time Range | select (string) | No | How far back Sentry should search. Available values: Past hour, Past 24 hours, Past 7 days, Past 14 days, Past 30 days. Default: 24h. | | Sort By | select (string) | No | How to order matching issues. Available values: Latest, Most frequent, Inbox, Newest, Recommended, Trending, Most users. Default: date. | | Maximum Issues | integer | No | A soft cap for issues returned across pages; the final page may make the result slightly larger. Minimum: 1. Maximum: 500. Default: 100. | | Cursor | string | No | Continue from a cursor returned by an earlier call. | #### Outputs | Field | Type | Description | | -------------- | ------------- | ---------------------------------------------------- | | Issues | object\_array | Structured Sentry issue records matching the search. | | Returned Count | integer | The number of issue records returned. | | Next Cursor | string | A cursor for continuing the issue search. | ### Get Issue Details Retrieve the current state and triage context for one issue. #### Inputs | Field | Type | Required | Description | | ------------ | --------------- | -------- | --------------------------------------------------------------------------------------- | | Organization | select (string) | Yes | The Sentry organization that owns the issue. Options load from the selected connection. | | Issue ID | string | Yes | The issue to inspect. | | Environment | string | No | Optionally filter issue context to an environment. | #### Outputs | Field | Type | Description | | ------------------- | ------------- | ---------------------------------------------------- | | Occurrence Count | integer | How many times Sentry has recorded the issue. | | Affected User Count | integer | How many users Sentry reports as affected. | | Culprit | string | The component or location associated with the issue. | | Project Slug | string | The Sentry project that owns the issue. | | Tags | object\_array | Structured tag summaries for the issue. | | Ownership | object\_array | Structured ownership records for the issue. | | Activity | object\_array | Structured recent activity for the issue. | | Issue ID | string | The Sentry issue ID. | | Title | string | The issue title. | | Status | string | The issue's current status. | | Priority | string | The issue's current priority. | | First Seen | datetime | When Sentry first observed the issue. | | Last Seen | datetime | When Sentry most recently observed the issue. | | Sentry URL | string | A link to the issue in Sentry. | ### Update Issue Change selected triage fields on a Sentry issue. #### Inputs | Field | Type | Required | Description | | ------------ | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------ | | Organization | select (string) | Yes | The Sentry organization that owns the issue. Options load from the selected connection. | | Issue ID | string | Yes | The issue to update. | | Status | select (string) | No | Optionally change the issue's triage status. Available values: Resolved, Unresolved, Ignored, Resolved in Next Release, Muted. | | Priority | select (string) | No | Optionally change the issue's priority. Available values: Low, Medium, High. | | Mark as Seen | boolean | No | Optionally mark the issue as seen or unseen. | | Bookmark | boolean | No | Optionally add or remove your bookmark. | | Subscribe | boolean | No | Optionally subscribe to or unsubscribe from issue updates. | #### Outputs | Field | Type | Description | | ---------- | ------- | ------------------------------------------------------ | | Issue ID | string | The updated issue ID. | | Status | string | The issue's resulting status. | | Priority | string | The issue's resulting priority. | | Seen | boolean | Whether the issue is marked as seen. | | Bookmarked | boolean | Whether the issue is bookmarked. | | Subscribed | boolean | Whether the connection is subscribed to issue updates. | ### List Project Events Review recent error events for a Sentry project. #### Inputs | Field | Type | Required | Description | | ------------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | Organization | select (string) | Yes | The Sentry organization that owns the project. Options load from the selected connection. | | Project | select (string) | Yes | The Sentry project whose events you want to review. Options load from the selected connection. | | Time Range | select (string) | No | How far back Sentry should search for events. Available values: Past hour, Past 24 hours, Past 7 days, Past 14 days, Past 30 days. Default: 24h. | | Include Full Event Bodies | boolean | No | Include full event payloads and stack traces. Default: false. | | Maximum Events | integer | No | A soft cap for events across pages; the final Sentry page can exceed it. Minimum: 1. Maximum: 500. Default: 100. | | Cursor | string | No | Continue from a cursor returned by an earlier call. | #### Outputs | Field | Type | Description | | -------------- | ------------- | --------------------------------------------------- | | Events | object\_array | Structured Sentry event records matching the query. | | Returned Count | integer | The number of event records returned. | | Next Cursor | string | A cursor for continuing the event search. | ### Create Release Register a Sentry release for one or more projects. #### Inputs | Field | Type | Required | Description | | ------------------------ | --------------- | -------- | ----------------------------------------------------------------------------------------------------- | | Organization | select (string) | Yes | The Sentry organization where the release will be created. Options load from the selected connection. | | Primary Project | select (string) | Yes | The main project associated with the release. Options load from the selected connection. | | Version | string | Yes | The unique release version. | | Additional Project Slugs | string | No | Optional comma-separated project slugs for a multi-project release. | | Git Reference | string | No | An optional commit SHA, tag, or branch for the release. | | Release URL | string | No | An optional external link for the release. | | Released At | datetime | No | When the release was deployed. | #### Outputs | Field | Type | Description | | ----------- | -------- | ------------------------------------------ | | Release ID | integer | The Sentry release ID. | | Version | string | The release version. | | Status | string | The release's current status. | | Created At | datetime | When Sentry created the release. | | Released At | datetime | When the release was deployed. | | Release URL | string | The external link attached to the release. | ## Triggers A trigger starts a workflow when its configured event occurs. Configure the event and filters before enabling the trigger. ### New Project Event Emit new error events after monitoring starts. Polls allow 30 seconds for indexing and recheck the past 10 minutes for late arrivals. Older late events are excluded. At most 10,000 event IDs are retained; larger windows fail without advancing. #### Configuration | Field | Type | Required | Description | | ------------------------- | --------------- | -------- | ----------------------------------------------------------------------------------------- | | Organization | select (string) | Yes | The Sentry organization that owns the project. Options load from the selected connection. | | Project | select (string) | Yes | The Sentry project to monitor. Options load from the selected connection. | | Include Full Event Bodies | boolean | No | Include full event payloads and stack traces. Default: false. | #### Event inputs | Field | Type | Required | Description | | --------------- | -------- | -------- | ----------------------------------------------- | | Event ID | string | Yes | The Sentry event ID. | | Title | string | Yes | The event title. | | Message | textarea | No | The event message. | | Project ID | string | Yes | The provider-assigned project ID for the event. | | Issue Group ID | string | No | The issue group associated with the event. | | Created At | datetime | Yes | When Sentry recorded the event. | | Full Event Body | string | No | The full Sentry event payload, when requested. | #### Outputs | Field | Type | Description | | --------------- | -------- | ----------------------------------------------- | | Event ID | string | The Sentry event ID. | | Title | string | The event title. | | Message | textarea | The event message. | | Project ID | string | The provider-assigned project ID for the event. | | Issue Group ID | string | The issue group associated with the event. | | Created At | datetime | When Sentry recorded the event. | | Full Event Body | object | The full Sentry event payload, when requested. | ## Important behavior Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data. The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.stackai.com/integrations/catalog/sentry.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.