Sentry setup guide

Agents work with your code, deployments and incidents.

Ways to connect

Company admins connect apps, on the Integrations page in Everdeck: open Sentry, choose one of the ways below, follow its steps and fill in its fields. Everdeck checks what you enter before it saves anything, and asks you to confirm it’s you (your second factor) before you type any secret. How connecting works.

Sentry can be connected 2 ways.

Internal integration token (recommended)

API key.

1. In Sentry, open Settings > Developer Settings > Custom Integrations, select Create New Integration, choose Internal Integration and select Next. (You need the Owner, Manager or Admin role in the organization.)
2. Name it "Everdeck". Leave Webhook URL empty and Alert Rule Action off: live updates from Sentry (starting work when an issue or comment changes, or an alert rule fires) aren't available yet.
3. Under Permissions choose Issue & Event: Read & Write, and Read for Project, Organization and Member (scopes event:read, event:write, project:read, org:read, member:read). Select Save Changes.
4. Copy the token from the Tokens section (internal integration tokens do not expire).
5. Paste your organization slug and the token into the form. If your organization stores data in the EU, change the Sentry address to https://de.sentry.io.

Field	What to enter
Sentry address (optional)	Web address. Starts as https://sentry.io. Use https://de.sentry.io if your organization stores its data in the EU, or your own address for self-hosted Sentry (no trailing slash).
Organization slug	Text. For example acme. The organization part of your Sentry address, for example acme in acme.sentry.io.
Auth token	A secret: Everdeck saves it encrypted and never shows it again.
Client secret (optional, not used yet)	A secret: Everdeck saves it encrypted and never shows it again. Live updates from Sentry aren't available yet; leave this empty.

Disconnecting deletes the credentials Everdeck saved, but Everdeck can't revoke them: the key, token or password itself keeps working at Sentry until you delete or rotate it there.

Personal token

API key.

1. Sign in as the Sentry user the agent should act as, open the account menu (top left) > Personal Tokens (https://sentry.io/settings/account/api/auth-tokens/) and create a new token.
2. Select the scopes event:read, event:write, project:read, org:read and member:read. Scopes cannot be changed later.
3. Paste your organization slug and the token into the form. The token stops working if this user leaves the organization.

Field	What to enter
Sentry address (optional)	Web address. Starts as https://sentry.io. Use https://de.sentry.io for EU organizations, or your self-hosted address.
Organization slug	Text. For example acme.
Personal token	A secret: Everdeck saves it encrypted and never shows it again. Where to find it.

Disconnecting deletes the credentials Everdeck saved, but Everdeck can't revoke them: the key, token or password itself keeps working at Sentry until you delete or rotate it there.

What agents can do

An agent uses an action only when its charter grants it, on the agent’s Tools tab, where you choose whether each one runs by itself (Auto), asks first or never runs. Each action has a risk tier: tier 3 actions, which customers or the public see, ask first unless you choose otherwise, and tier 4 actions (money, deleting things, access) always need a person. How tools and tiers work.

Actions marked Reads outside content return things people outside your company may have written. Agents treat what they read as information, never as instructions, and their riskier actions later in the same session need approval.

• List projectsTier 0 · ReadReads outside contentsentry_list_projects

  List the organization's projects with id, slug, name and platform.

• Find issuesTier 0 · ReadReads outside contentsentry_list_issues

  List the organization's issues with Sentry search syntax, for example "is:unresolved level:error", "is:unresolved assigned:me", "release:1.4.0 is:unresolved" or "is:unresolved firstSeen:-24h". Returns short id, title, culprit, level, status, priority, event and user counts, first and last seen, assignee and project. Sorted by last seen unless sort says otherwise.

• Look up an issue by short idTier 0 · ReadReads outside contentsentry_resolve_short_id

  Turn a short id such as BACKEND-1A3 (as shown in Sentry, alerts and commit messages) into the issue id the other actions use.

• Read an issueTier 0 · ReadReads outside contentsentry_get_issue

  Read one issue: title, culprit, level, status and substatus, priority, event and user counts, first and last seen, first and last release, assignee, comment count and link.

• Read an issue's stack traceTier 0 · ReadReads outside contentsentry_get_issue_event

  Read one event of an issue, rendered as Markdown for reading: the exception and stack trace, breadcrumbs, request, tags and context. event_id may be latest, oldest, recommended (the most useful example) or a specific event id.

• See what an issue affectsTier 0 · ReadReads outside contentsentry_get_tag_values

  Show how an issue's events spread over one tag: the top values with counts and when each was last seen. Useful keys include release, environment, browser, os, device, url, transaction, server_name and user.

• Resolve, archive, prioritise or assign an issueTier 2 · ReversibleReads outside contentsentry_update_issue

  Change an issue's state. Examples: resolve {"status": "resolved"}; resolve in the next release {"status": "resolvedInNextRelease"}; reopen {"status": "unresolved", "substatus": "ongoing"}; archive until it gets worse {"status": "ignored", "substatus": "archived_until_escalating"}; assign {"assignedTo": "[email protected]"} or {"assignedTo": "team:12"}; set priority {"priority": "high"}. Subscribers are notified.

• List releasesTier 0 · ReadReads outside contentsentry_list_releases

  List releases, newest first, with version, when they were created and released, how many new issues each introduced, projects and last deploy.

• List membersTier 0 · ReadReads outside contentsentry_list_members

  List organization members with name, email, role and user id (use "user:<user id>" or the email to assign issues). Search with query, for example "email:[email protected]".

Testing, problems and disconnecting

Everdeck checks the connection when you save it. On the connection’s page in Integrations, Test checks it again at any time.

If Sentry later refuses the connection, for example because a key was deleted or a sign-in expired, the connection shows Needs attention on the Integrations page and the people who manage connections are told. Agents can’t use it until a company admin fixes it with Edit.

To stop agents using Sentry, open the connection and select Disconnect. Agents stop using it at once and its saved credentials are deleted. What else happens depends on how it was connected: each way above says.