Skip to main content
The Sentry integration connects your Sentry organization to Modem. It ingests user feedback into conversations and topics, and it gives the Modem Agent live access to your errors: search issues, read stack traces and sample events, and (with your approval) resolve, assign, or reprioritize them.
Sentry errors and issues are not ingested. The agent queries them live when you ask. Only user feedback submitted through Sentry is stored in Modem. See What Gets Captured.

​
How it works

Modem connects to Sentry as a published Sentry Integration Platform app, installed once for your Sentry organization. A Sentry admin approves the installation, and installing the app is also what grants Modem access. There is no separate authorization step. Modem stores the installation’s access token encrypted and refreshes it automatically in the background, so the connection normally stays authenticated without any action from you. Each Modem organization connects to one Sentry organization. When you ask the agent about Sentry, it calls Sentry’s REST API with that connection’s credentials, scoped to the connected Sentry organization only.

​
What Gets Captured

Only user feedback submitted through Sentry is ingested into Modem. Each report becomes a conversation that can group into topics. Sentry errors and issues stay in Sentry. They do not appear on the Topics page. When you ask about them, the agent queries Sentry live and the result stays in that chat.

​
Prerequisites

  • Owner or admin role in your Modem organization, to connect and manage the integration
  • A Sentry admin to approve the app installation in your Sentry organization

​
Setup

1

Start the connection

Go to Settings → Integrations → Sentry in your Modem dashboard and click Connect. Only organization owners and admins can connect.
2

Approve the installation in Sentry

You’ll be redirected to Sentry’s install page for the Modem app. A Sentry admin approves the installation there, which also grants Modem access in the same action.
3

Confirm the connection

Sentry redirects you back to Modem automatically once the app finishes installing. The settings page shows the connected Sentry organization.
4

Ask the agent

Ask the Modem Agent about your errors from the web dashboard, Slack, or anywhere else you talk to it. See Working with Sentry Data below.

​
Working with Sentry Data

Once connected, the agent can reach Sentry’s REST API on your behalf. Common things to ask for:
  • Search issues: unresolved errors, new regressions, issues on a specific release or environment, the noisiest unassigned issues
  • Dig into one issue: title, culprit, event and affected-user counts, stack traces and breadcrumbs from sample events
  • Review user feedback: reports submitted through Sentry’s user feedback feature
  • Size a problem: how many events and users an issue touched, and over what window

​
Taking action

The agent can also change things in Sentry: resolve or ignore an issue, assign it to a person or team, or set its priority. Every write requires your explicit approval first. The agent shows you exactly what will change and waits for you to confirm before it calls Sentry. Read-only queries never require approval.

​
Permissions

Modem accesses:
  • Issues and error events
  • User feedback items
  • Project metadata
Modem does not access:
  • Source code
  • Organization billing information
  • Sentry account credentials
Everything the agent reads is scoped to the single Sentry organization the app was installed in.

​
Troubleshooting

The person approving the installation needs admin rights in your Sentry organization. Ask a Sentry admin to complete the install step.
Either Sentry was never connected for your organization, or the installation was removed on the Sentry side and the stored token was revoked. Reconnect from Settings → Integrations → Sentry.
A 403 from Sentry means the installation’s scopes don’t cover that change. Reads keep working. If your team needs a write the app can’t perform, contact support@modem.dev.
That’s expected: only user feedback is ingested into Modem’s conversations and topics. Sentry errors and issues are not, so ask the agent about them directly instead. If feedback submitted after you connected Sentry isn’t appearing either, contact support@modem.dev.

​
Disconnecting

To disconnect Sentry:
  1. Go to Settings → Integrations → Sentry
  2. Click Disconnect and confirm
Disconnecting removes Modem’s connection to your Sentry organization and its stored credentials. The agent can no longer query or change Sentry. To also revoke Modem’s access on the Sentry side, uninstall the Modem app from your Sentry organization’s integration settings. User feedback already ingested into conversations and topics stays in Modem. Sentry errors and issues were never stored here, so disconnecting only stops live lookups. Historical data remains in Modem after disconnecting. Nothing is changed in Sentry itself.

The Modem Agent

Query and act on your data, including your connected Sentry organization.

Topics

See how ingested Sentry user feedback is grouped into themes.

GitHub

Sync issues and pull requests for shipping context alongside your errors.

All Integrations

Browse every data source and agent tool.