Sanaf AI
Start free
Developer Tools

Sentry, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Sentry account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Signs in to your account
  • 100 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Sentry is

Integrate Sentry to manage your error tracking and monitoring.

You sign in with your own Sentry account, the same way you already do. We never see or hold your password.

How a run works

One message in, the work done in Sentry.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Sentry. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Sentry account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

100 tools it already has

What it can do in Sentry

These are the ready-made tools your AI employee already has in Sentry. It is not limited to them, but it never has to be taught these.

  • Access project informationRetrieves detailed information for a sentry project, given its existing organization and project id or slug.
  • Add a symbol source to a projectAdds a new custom symbol source (http, gcs, or s3) to a project for fetching debug symbols; if an id is provided, it must be unique for the project and not start with 'sentry:'.
  • Add or remove user email by idAdds or removes a secondary email for an existing sentry user, determined by whether the email already exists for that user.
  • Add organization member via emailInvites a new member (or re-invites an existing non-accepted member) to a sentry organization via email, allowing specification of organization and team roles.
  • Add team member in organizationAdds an existing member of an organization to one of its teams; the member must already belong to the organization, and the team must also belong to that organization.
  • Add team to projectGrants a sentry team access to a sentry project within the specified sentry organization.
  • Create an external teamLinks an external team or channel (e.g., slack, github) to an existing sentry team, using a pre-configured integration for the specified provider and its valid sentry integration i
  • Create dashboard with widgetsCreates a sentry dashboard with widgets for an organization; organization id or slug and specified project ids must be valid, and start/end datetimes (if absolute range) must form
  • Create external user for organizationLinks a sentry user to an external identity provider's user within a sentry organization; the sentry user must be an organization member, an active integration for the provider mus
  • Create organization alert ruleCreates a sentry metric alert rule for an organization, mandating a 'critical' trigger, typically for a single project, where actions may require sentry integrations.
  • Create organization monitorCreates a new monitor (type 'cron job') within a sentry organization to track scheduled tasks, allowing configuration of its name, slug (which must be unique if provided), status,
  • Create organization teamCreates a new team in a sentry organization, requiring either a 'slug' (preferred, as 'name' is deprecated) or 'name' to define the team.
  • Create project key with optional rate limitingCreates a new client key (dsn) for an existing sentry project, with optional custom rate limit configuration.
  • Create project rule for alertsCreates a sentry project alert rule by defining conditions, actions, and optional filters using specific json structures (detailed in parameter descriptions) to automate responses
  • Create project webhook subscriptionRegisters a new webhook subscription for a sentry project to send http post notifications to a specified url for given events, provided the project has the 'servicehooks' feature e
  • Create release deploy for orgCreates a new deploy record in sentry to track the introduction of a release version into a specific environment.
  • Create release for organizationCreates a new sentry release for an existing organization, associating it with specified projects that must belong to that organization.
  • Create scim group for organizationCreates a new sentry team (scim group) within an organization where scim is enabled; a url-friendly slug is auto-generated from the displayname (e.g., 'my team' becomes 'my-team' b
  • Create sentry external issue linkLinks an existing sentry issue to an issue in an external service, or updates an existing link, requiring a configured sentry app installation uuid.
  • Create team project for organizationCreates a new sentry project for an existing organization and team, allowing configuration of its name, slug, platform, and default alert rules.
  • Create user for SAML integrationCreates a new sentry organization member via a scim request for saml integration; this action does not support setting secondary emails.
  • Deactivate an organization memberDeactivates and permanently deletes a sentry organization member by using a scim patch operation to set their 'active' attribute to 'false'.
  • Delete a project symbol sourceDeletes a specific custom symbol source from a project.
  • Delete a team from an organization (SCIM v2)Permanently and irreversibly deletes a specific team from a sentry organization via a scim v2 request, provided scim integration is enabled for the organization.
  • Delete an external team by idUnlinks a previously established external team from a sentry team; this action does not delete either the sentry team or the external team.
  • Delete dsyms for projectPermanently removes a specific debug information file (dif), used for symbolicating crash reports, from the specified sentry project and organization.
  • Delete external issue by uuidUnlinks an external issue (e.g., from jira/github), identified by external issue id, from the sentry app installation specified by uuid.
  • Delete external user from organizationDeletes the link between an external user (e.g., from an sso provider) and a sentry user within the specified sentry organization.
  • Delete member from teamRemoves an organization member from a sentry team, revoking their team-specific permissions, provided the member is currently part of that team.
  • Delete org notification actionDeletes a specific spike protection notification action for a sentry organization, where action id must be a valid action associated with the organization id or slug.
  • Delete organization alert ruleDeletes a specific metric alert rule within a sentry organization.
  • Delete organization dashboardDeletes a custom dashboard or tombstones (marks as deleted) a pre-built dashboard within a sentry organization.
  • Delete organization discover queryPermanently removes a specific saved discover query (a configuration for exploring event data) from a sentry organization.
  • Delete organization integrationPermanently deletes a specific integration previously installed for the sentry organization.
  • Delete organization issuePermanently deletes a specific sentry issue, identified by its id, from an organization; this operation is irreversible and idempotent.
  • Delete organization memberPermanently removes a member from a sentry organization, revoking their access to that organization and all its associated projects.
  • Delete organization monitorDeletes a sentry cron monitor or, if environment is specified, only specific environments within that monitor.
  • Delete organization releasePermanently and irreversibly removes a sentry release, including all its associated files, identified by its version from the specified organization.
  • Delete project by idSchedules a sentry project for asynchronous deletion within a specified organization, hiding it from most public views once the process begins.
  • Delete project hookDeletes a specific service hook from a sentry project using its organization, project, and hook identifiers.
  • Delete project issuesPermanently removes specified issues from a sentry project; if no issue ids are provided, it removes the oldest 1000 issues.
  • Delete project keyPermanently deletes a specific client key (dsn) for a project, preventing it from being used to send events to sentry.
  • Delete project monitorDeletes a sentry monitor, or optionally only its specified environments, for a given project.
  • Delete project replayPermanently deletes a specific sentry session replay (a video-like reproduction of user interactions, including console logs and network activity) from the specified project and or
  • Delete project rulePermanently deletes a specific issue alert rule from an existing project within an existing sentry organization.
  • Delete project team associationRevokes a team's access to a sentry project; this operation is idempotent.
  • Delete release filePermanently deletes a specific file from an existing release, project, and organization; this action is idempotent.
  • Delete release file by idPermanently deletes a specific build artifact (e.g., source map, application bundle) associated with a release.
  • Delete team by organization and team slugSchedules a sentry team for asynchronous deletion, which releases the team's slug for reuse upon successful scheduling.
  • Delete user emails by idPermanently removes a sentry user's email address; if multiple emails exist, sentry's api logic (e.g., primary or previously marked) determines which is deleted.
  • Delete user from orgRemoves a scim-managed member from a sentry organization that has scim enabled, permanently revoking their access.
  • Enable spike protection for an organizationEnables or updates spike protection for specified projects (or all projects using ['$all']) within an existing sentry organization, to which the projects must belong.
  • Fetch issue event by idRetrieves the 'latest', 'oldest', or 'recommended' event for a sentry issue, optionally filtered by environment(s).
  • Fetch organization alert rulesRetrieves a list of active metric alert rules for an existing sentry organization, identified by its id or slug.
  • Fetch organization release threshold statusesRetrieves derived health statuses for release thresholds in a sentry organization for a given time range, optionally filtered by environment, project, or release; start and end tim
  • Fetch organization replay countRetrieves the total count of session replays for a specified sentry organization, filterable by time range, environment, project, and query.
  • Fetch organization replay detailsRetrieves detailed information for a specific replay session by id within a sentry organization, optionally filtering time-series data using statsperiod or start/end, and further r
  • Fetch organization replay selectorsFetches replay selectors (css selectors for session replays) for a sentry organization, filterable by various criteria; use either statsperiod or start/end for time range, not both
  • Fetch project environment detailsRetrieves detailed information for a specific environment within a sentry project.
  • Fetch project ownership detailsRetrieves the ownership configuration, like codeowners rules or issue owner settings, for a specified sentry project.
  • Fetch project release filesRetrieves artifact files (e.g., source maps, debug information files) for a specific release version in a sentry project; requires existing organization, project, and release versi
  • Fetch project replay clicksFetches a list of user click interactions for a specific sentry session replay, including the clicked dom element id and timestamp.
  • Fetch replay recording segmentRetrieves a specific recording segment for a sentry replay, requiring valid organization, project, replay, and segment identifiers.
  • Get activation of alert rule for organizationRetrieves all activations (triggered instances) for a specific metric alert rule within a sentry organization.
  • Get integration details by orgRetrieves details for a specific integration, identified by integration id, installed within an existing sentry organization, identified by organization id or slug.
  • Get organization by id or slugRetrieves a sentry organization by its id or slug; use the detailed parameter to optionally exclude project and team details for a more concise response.
  • Get organization detailsRetrieves sentry organizations accessible via the current authentication, with scope varying between user (all in region) and api key (linked org only) credentials.
  • Get organization environmentsRetrieves a list of deployment environments (e.g., 'production', 'staging') for a sentry organization, optionally filtering by visibility.
  • Get organization issue detailsRetrieves detailed information for a specific issue within a sentry organization.
  • Get organization monitor by id or slugRetrieves detailed information for a specific monitor (e.g., a cron job or scheduled task) within an organization.
  • Get organization release versionRetrieves detailed information, including optional health data and statistics, for a specific release version within a sentry organization.
  • Get organization sessionsRetrieves time series data for an organization's sentry project release health sessions; note session duration data (e.g., using avg(session.duration)) may be incomplete after jan
  • Get organization stats summaryRetrieves summarized event statistics for a sentry organization, aggregated by project, allowing queries for event counts or unique occurrences over a specified time period and res
  • Get project event statsRetrieves event statistics for a specified sentry project, returning data as [timestamp, count] pairs; ensure since precedes until if both are provided.
  • Get project eventsRetrieves a list of error events for a specified project within a sentry organization, with options for pagination and detail level.
  • Get project hookRetrieves detailed information for an existing service hook, identified by hook id, within a specific sentry project and organization.
  • Get project listRetrieves a list of sentry projects (representing monitored applications or services), useful for discovery or selecting a project for subsequent operations.
  • Get project monitor by idRetrieves detailed information for a specific sentry cron monitor, provided the organization, project, and monitor exist.
  • Get project rule detailsRetrieves detailed information for a specific issue alert rule within a sentry project.
  • Get scim group by team idRetrieves scim group information for a sentry team, if scim is enabled for the organization; the 'members' list in the response is limited to 10,000 entries.
  • Get sentry app installations for organizationRetrieves a list of sentry app installations for a given organization, which must exist.
  • Get team members by id or slugRetrieves a list of all active members for a sentry team, excluding users with pending invitations.
  • Get who viewed replay by projectRetrieves users who viewed a specific, existing session replay within a sentry project and organization.
  • List organization dashboardsRetrieves a list of custom dashboards for a sentry organization, with pagination support.
  • List organization membersLists all members, including those with pending invitations, for a sentry organization.
  • List organization releasesRetrieves a list of releases for an existing sentry organization, optionally filtering by a query string that matches the start of the release version.
  • List organization repositoriesRetrieves a list of version control repositories for a specific sentry organization, which must exist and is identified by its id or slug.
  • List organization user teamsRetrieves a list of all teams that the authenticated user has access to within the specified sentry organization.
  • List project usersRetrieves users who have interacted with or are recognized within a specific sentry project, optionally filtered by a query.
  • List SCIM v2 organization usersRetrieves a paginated list of scim (system for cross-domain identity management) users for a sentry organization, allowing for filtering, pagination, and attribute exclusion.
  • List teams in organizationLists teams for an existing sentry organization, optionally including project details and supporting pagination via a cursor.
  • Modify organization monitor dataUpdates an existing sentry monitor's properties, requiring name and type (must be 'cron job'), and optionally slug, status, owner, or is muted state for a monitor within the specif
  • Modify organization notification actionModifies an organization's notification action, specifically for spike-protection triggers.
  • Modify organization settingsUpdates settings for a sentry organization, such as name, slug, member roles, privacy, and integrations; if avatartype is 'upload', avatar (base64 image) is required.
  • Modify release file attributesUpdates attributes (e.g., name, distribution) of a specific file within an existing release, identified by organization, version, and file id.
  • Patch SCIM group operationsPerforms scim patch operations (rfc 7644) to update attributes of a scim-enabled sentry team, provided scim integration is active for the organization.
  • Retrieve alert rule detailsRetrieves detailed information for a specific metric alert rule within a sentry organization.
  • Retrieve an organization's repository commitsRetrieves a list of commits for a given repository within a sentry organization.
  • Retrieve commit files for releaseRetrieves files changed in commits for a specified sentry release; the release must exist and have linked commits.
  • Retrieve dsym files for projectRetrieve a list of debug information files (dsym files) for a specified sentry project, used for symbolication to display human-readable stack traces.
Access, and who is in charge of it

You stay the boss of your Sentry account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Sentry account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Sentry is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Sentry and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Sentry

Can an AI employee really work inside Sentry?
Yes. It signs in to your own Sentry account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Sentry?
No. Nothing moves and nothing is replaced. Your records stay in Sentry, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Sentry account?
You sign in with your own Sentry account, the same way you already do. We never see or hold your password. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Sentry?
It has 100 ready-made tools in Sentry today, among them Access project information, Add a symbol source to a project and Add or remove user email by id. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Sentry and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Sentry and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Sentry?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Sentry is written down with what it did and when.