Sentry Setup Beta

If your team builds and runs its own apps -- client portals, automation services, internal tools -- connect the Sentry organization that monitors them. The agent can then search Sentry issues, read the stack trace and breadcrumbs behind an error, see who owns a project, and -- with approval -- resolve, archive, reopen, or assign issues.

Sentry is an Internal integration: it connects your MSP's own Sentry organization, not your customers'. It appears under Internal on the Integrations page, next to Slack and Microsoft Teams. Junto supports one Sentry organization per Junto organization.

Prerequisites

• A Junto Admin or Owner account
• A Sentry organization, on Sentry's cloud or self-hosted
• Permission in Sentry to create an internal integration or a personal auth token

Step 1: Create a Sentry Auth Token

Use either option:

• Internal integration token (recommended) -- In Sentry, go to Settings > Custom integrations, create an internal integration (for example named Junto), and copy its token. The token isn't tied to one person's account.
• Personal token -- Create a personal auth token with the org:read, event:read, event:write, and member:read scopes.

Store the token securely.

Step 2: Configure in Junto

1. Go to Settings > Integrations, and under Internal, open Sentry.

2. Click Add configuration.

3. Complete the form:

   Field	What to enter
   Organization slug	The short name in your Sentry address, like acme in acme.sentry.io
   Auth token	The token from Step 1. It is encrypted when stored.
   Sentry URL	Keep https://sentry.io for Sentry's cloud in any region. Enter your server's address only for self-hosted Sentry.
   Active	Leave on. Turn it off later to pause agent access without deleting the connection.

4. Click Create configuration. Junto checks the token against your Sentry organization before saving. For Sentry's cloud, Junto detects your organization's data region automatically.

5. Click Test connection on the configuration card to confirm the connection.

The configuration card shows the Sentry organization name, its slug and host, and the last four characters of the token.

What the Agent Can Do

Capability	What Junto can do	Risk level
Search issues	Search with Sentry's issue search, such as is:unassigned level:error, release:1.2.0, or age:-24h; filter by project, environment, and time period. Unresolved issues by default	Low
Get issue	Read an issue's status, level, priority, event and user counts, first and last seen, releases, assignee, tags, and recent activity. Accepts an ID, a short ID like API-1Z, or an issue URL	Low
Get issue event	Read what happened in one event -- the recommended, latest, or oldest, or a specific event ID: exception, stack trace with source lines for your app's own code, breadcrumbs, request, release, environment, and runtime contexts	Low
List projects	List projects with platform, owning teams, environments, and latest release	Low
List members and teams	Find the people and teams an issue can be assigned to	Low
Update issue	Resolve, resolve in the next release, reopen, or archive an issue (until it escalates, or forever), and assign it to a member by email or to a team	Medium

All write actions require technician approval before execution. Read-only tools do not require approval.

Scope and Behavior

• Explore only: Sentry tools are available in Explore chat. They aren't used in ticket chat or during automatic ticket triage.
• Stack traces: Up to 30 frames per exception are returned, with source lines only for your app's own frames. The affected user's IP address is never included.
• Assignments: Members are assigned by email and teams by slug. Pending invites can't be assigned, and clearing an assignee isn't supported -- reassign the issue instead.
• No comments: The agent can't add comments to Sentry issues.

Example requests:

• "What new errors showed up in the client portal in the last 24 hours?"
• "Show me the stack trace for API-1Z and explain the likely cause."
• "Which unresolved issues in the backup-agent project are unassigned?"
• "Resolve API-1Z in the next release and assign it to the platform team."

Managing the Connection

• Update the configuration: Click Edit, change the slug, token, or URL, and click Update configuration. Leave Auth token blank to keep the stored token. Junto re-checks the connection when the slug or URL changes.
• Pause the integration: Click Edit, turn off Active, and save.
• Disconnect: Click Disconnect and confirm. This removes Junto's saved auth token. Nothing changes in Sentry.

Troubleshooting

• Save fails with an authentication error -- Check that the token hasn't been revoked and belongs to the organization in Organization slug.
• Save fails on the Sentry URL -- For Sentry's cloud, keep https://sentry.io, even if your organization is in the EU region. For self-hosted Sentry, use your server's public HTTPS address.
• Issues can be read but not updated -- A personal token needs the event:write scope. Create a new token with all four scopes, or use an internal integration token.
• An assignment was refused -- The member may still be a pending invite in Sentry, or the email or team slug doesn't match. Ask the agent to list members or teams first.
• The agent doesn't use Sentry in ticket chat -- Sentry tools are only available in Explore chat.