Menu

Mattering Automations Sentry integration

Connect Sentry to Mattering Automations: issues, events, releases, deploys, projects, teams, and alert rule audits as workflow steps, authenticated with a Sentry auth token sent as a Bearer credential.

The Mattering Automations Sentry integration adds Sentry to your automation canvas: search and triage issues with Sentry's structured query syntax, read the events and tag breakdowns underneath them, create releases and record deploys, manage projects and read their client keys, list teams and members for assignment lookups, and audit issue and metric alert rules.

Setup takes a few minutes: create an auth token in Sentry, attach it as a credential in Mattering, and test the connection. This guide walks through each step and ends with the full node reference.

The surface is read-heavy by design: 24 of the 33 nodes are queries, and the triage workhorse Sentry: Update Issue makes only reversible changes (resolve, ignore, assign, set priority; set the field back to undo). The only destructive nodes are the two issue deletes, which queue permanent, asynchronous removal with no undo, and the bulk form requires explicit issue ids because the raw API's filter-wide delete is deliberately not exposed.

Before you start

  • A Sentry account with an organization. The free Developer plan is enough; the integration behaves the same on paid plans.
  • Permission to create a User Auth Token (Settings > Account > API > User Auth Tokens) or an internal integration token in the organization's Developer Settings.
  • A Mattering workspace with access to the Automations app.
  • If your organization lives in Sentry's EU region or on a self-hosted install, have its hostname ready (for example de.sentry.io), to set in the optional host field the nodes carry.

Create a Sentry auth token

Mattering authenticates to Sentry with an auth token sent as a Bearer credential on every request. Two token types give full coverage of this integration: a User Auth Token, which acts as you with scopes chosen at creation, and an internal integration token, which acts as the organization with scopes editable after creation. The internal integration is the better choice for a shared automation credential, because a User Auth Token stops working if the person who created it leaves the organization.

In Sentry, open User Auth Tokens (Settings > Account > API > User Auth Tokens), or create an internal integration under the organization's Developer Settings.
Grant the scopes your automations need: org:read, project:read, team:read, event:read, and event:write cover triage; add project:write, member:read, and project:releases for the full surface, and event:admin only if the delete nodes will be used.
Copy the token.
Do not use an Organization Token (the kind under Developer Settings > Organization Tokens). Its permissions are fixed for CI release tasks and cannot be customized: the release and deploy nodes respond, but issue, event, member, and stats reads return 403. A token that looks valid yet 403s on almost everything is nearly always one of these.

Connect Sentry to Mattering

In Mattering Automations, open Connectors and click Add Connector.
Choose Sentry from the list.
Click Create new credential, paste your auth token, and save.
The credential is stored encrypted in Google Secret Manager and never appears in workflow logs.
Click Test Connection: Mattering calls Sentry's organizations endpoint, a zero-parameter read that confirms the token authenticates.
Click Connect. All 33 Sentry nodes appear in your canvas palette.

Verify it works

After connecting, open any automation canvas and check the palette: a Sentry section should list the query and action nodes. Drop Sentry: List Organizations onto the canvas and run a test step. It takes no parameters and is a safe, read-only call; a successful response lists the organizations the token can see, and the organization slug it returns is what every other node needs.

To confirm the rest of the surface, run Sentry: List Projects with that slug, then Sentry: List Project Issues against a project (the default query is is:unresolved). Everything in the verify path is read-only; nothing here can modify or delete anything in Sentry.

Node reference

33 nodes, generated from the connector itself so this reference always matches what ships.

Read and query nodes 24

Sentry: Get Issue

sentry_get_issue

Retrieve one issue's full details: status, substatus, priority, assignee, counts, first and last seen. Use Sentry: Resolve Short ID first if you only have the BACKEND-API-1A form. Requires event:read.

Sentry: Get Issue Event

sentry_get_issue_event

Retrieve one event of an issue, with full detail including tags and entries. event_id accepts the special values latest (the default here), oldest, and recommended as well as a specific 32-character event ID, so with an empty event_id this node returns the issue's latest event, the standard "show me the newest occurrence" step. Requires event:read.

Sentry: Get Organization

sentry_get_organization

Retrieve one organization's full details: settings, feature flags, access, and (unless detailed is 0) its teams and projects. Requires org:read.

Sentry: Get Organization Event Counts

sentry_get_organization_stats

Retrieve event counts for an organization (the stats_v2 endpoint): time series of accepted, filtered, and dropped events, groupable by outcome, category, reason, or project. The quota and volume view, for usage digests and spike alerts. Requires org:read.

Sentry: Get Project

sentry_get_project

Retrieve one project's full details: platform, teams, features, and settings such as digest delays and resolve age. Requires project:read.

Sentry: Get Project Event

sentry_get_project_event

Retrieve one event by its 32-character hexadecimal event ID (as reported by the SDK client), with full detail. Use this when a workflow starts from an event ID, for example out of a webhook or a log line. Requires project:read.

Sentry: Get Release

sentry_get_release

Retrieve one release with commit and deploy counts, optionally including release health data (crash-free sessions and users) when health is true. Requires project:releases or project:read.

Sentry: Get Team

sentry_get_team

Retrieve one team's details, including member count and the acting token's access. Requires team:read.

Sentry: List Issue Alert Rules

sentry_list_issue_alert_rules

List a project's issue alert rules: conditions, actions, and frequency for the when-an-issue-matches alerts. Read-only auditing surface; rule mutation is deliberately not exposed here. Sentry's docs mark this endpoint deprecated in favor of the newer alerts APIs, but it remains live and is the stable list form. Requires alerts:read or project:read.

Sentry: List Issue Events

sentry_list_issue_events

List the individual error events grouped under one issue. By default returns event summaries; set full to include the complete event body with stacktrace (much larger output, page accordingly). Requires event:read.

Sentry: List Issue Tag Values

sentry_list_issue_tag_values

List the values of one tag across an issue's events, with per-value counts: which browsers, releases, URLs, or users an issue actually hits. Requires event:read.

Sentry: List Metric Alert Rules

sentry_list_metric_alert_rules

List an organization's metric alert rules: the threshold-based alerts over error counts, sessions, and performance metrics, with their triggers and thresholds. Read-only auditing surface. Requires alerts:read or org:read.

Sentry: List Organization Issues

sentry_list_organization_issues

List issues across a whole organization, filterable to specific projects and environments, with the same structured search syntax as the project-level list. The org-wide triage view for daily digests and escalation sweeps. Requires event:read.

Sentry: List Organization Members

sentry_list_organization_members

List an organization's members with email, name, org role, and invite status. The member id returned here is what member-management endpoints take; the assignedTo field on issue updates takes the USER's id, username, or email instead. Requires member:read.

Sentry: List Organizations

sentry_list_organizations

List the Sentry organizations the auth token can see, with slug, name, and status for each. Needs no parameters at all, which makes it both the credential health check and the natural first step of any Sentry workflow: every other node needs the organization slug this returns. A user token lists the user's organizations; an internal-integration token lists its own organization. Requires the org:read scope.

Sentry: List Project Client Keys

sentry_list_project_keys

List a project's client keys (DSNs), the ingestion endpoints SDKs send events to. Each key carries its public DSN and rate limit settings. DSNs authorize event INGESTION only, not API reads, but treat the output with care anyway. Requires project:read.

Sentry: List Project Events

sentry_list_project_events

List a project's error events across all its issues, newest first, optionally windowed by time. Event streams for audit trails and export flows; for triage, the issue lists are usually the better unit. Requires project:read.

Sentry: List Project Issues

sentry_list_project_issues

List a project's issues (error groups) with Sentry's structured search syntax. The default query is is:unresolved; combine filters like is:unresolved level:error release:backend@2.4.1 assigned:me. Returns issue id, short id, title, status, and counts; the issue id feeds the get, update, delete, and event nodes. Requires event:read.

Sentry: List Projects

sentry_list_projects

List an organization's projects with slug, platform, and team. The project slug returned here is what the project-scoped issue, event, key, and alert nodes take. Requires org:read.

Sentry: List Release Deploys

sentry_list_release_deploys

List a release's deploys: which environments it went to and when. Requires project:releases or project:read.

Sentry: List Releases

sentry_list_releases

List an organization's releases, newest first, filterable by project and environment. query is a case-insensitive substring match on the version. Requires project:releases or project:read.

Sentry: List Team Projects

sentry_list_team_projects

List the projects a team owns. Useful before Sentry: Create Project to see what already exists under the team. Requires project:read.

Sentry: List Teams

sentry_list_teams

List an organization's teams. The team slug returned here feeds Sentry: Create Project and team:<id> issue assignment. Requires team:read (org:read also grants it).

Sentry: Resolve Short ID

sentry_resolve_short_id

Translate a human-facing short ID like BACKEND-API-1A (the form Sentry shows in the UI, commit messages, and chat links) into the numeric issue ID and project slug that the issue and event nodes need. Requires event:read.

Action nodes 9

Sentry: Bulk Delete Issues

sentry_bulk_delete_issues

DESTRUCTIVE: queue a list of a project's issues for permanent deletion, groups and events both, with no undo. This node REQUIRES an explicit id list on purpose: the raw API deletes by status filter when ids are omitted, and that project-wide wipe is deliberately not exposed on the canvas. Requires event:admin.

Sentry: Bulk Update Issues

sentry_bulk_update_issues

Mutate several of a project's issues in one call: pass issue IDs and the fields to set (typically status: resolved to close out a list). CAUTION: when the id list is omitted the API applies the change to the project's issues matching the status filter (up to its internal bulk limit), so always set ids unless a sweeping change is intended. IDs outside the project are silently ignored, per the docs. Field changes are reversible; the merge flag is not cleanly so (unmerging is manual). Requires event:write.

Sentry: Create Deploy

sentry_create_deploy

Record a deploy of a release to an environment, which timestamps the release for that environment and triggers deploy notifications. Note: deploys cannot be deleted via the API, so a test deploy on a scratch release leaves a permanent (harmless) record. Requires project:releases (or org:ci), so this also works with an organization token.

Sentry: Create Project

sentry_create_project

Create a new project under a team. Note the team-scoped path: Sentry creates projects via a team, not directly on the organization. Returns the created project object; list its DSN with Sentry: List Project Client Keys to start sending events. Requires project:write.

Sentry: Create Release

sentry_create_release

Create a release for one or more projects, so events tag themselves to it and regressions can say which version reintroduced them. Idempotent-ish: creating an existing version again updates its project associations rather than failing. Follow with Sentry: Create Deploy to record where it shipped. This is the surface Sentry's own org tokens are scoped for, so it works with all three token types. Requires project:releases (or org:ci).

Sentry: Delete Issue

sentry_delete_issue

DESTRUCTIVE: queue one issue for permanent deletion, removing the group and all its events. The API answers 202 Accepted and deletes asynchronously; there is no undo. Prefer Sentry: Update Issue with status resolved or ignored unless the data itself must go. Requires event:admin.

Sentry: Update Issue

sentry_update_issue

Update one issue: resolve, unresolve, or ignore it, assign it to a user or team, set its priority, bookmark or subscribe. Only the fields you set are changed, and every change here is reversible by setting the field back. The workhorse of Sentry triage automations. The raw API also accepts merge and discard flags via extra_body; discard deletes future events for the issue, so treat it as destructive if used. Requires event:write.

Sentry: Update Project

sentry_update_project

Update a project's settings: rename, change the slug or platform, bookmark it, set the mail subject prefix, or the auto-resolve age in hours. Only the fields you set are changed. Requires project:write for most fields. Careful with slug changes: existing URLs and configs referencing the old slug break.

Sentry: Update Release

sentry_update_release

Update an existing release's metadata: ref, URL, release date, or attached commits. The version itself cannot be renamed. Requires project:releases.

Using the integration

On the automation canvas

Sentry nodes chain with every other node: a scheduled Sentry: List Organization Issues sweep can open a task in Mattering Productivity for each new unresolved error, Sentry: Get Organization Event Counts can feed a volume digest into a Mattering database, and Sentry: Create Release followed by Sentry: Create Deploy can annotate what shipped straight from a deploy pipeline.

From AI assistants over MCP

Every node speaks MCP, the open protocol for connecting AI assistants to tools. Claude, ChatGPT, and Matter can search issues, read stacktraces, and check release health through the same nodes your workflows use. Sentry also ships an official MCP server of its own; the advantage here is that these identical tools double as workflow steps, so what an agent looks up, an automation can act on. The 24 query nodes are the safest surface to hand an agent.

Issue triage with the update nodes

Sentry: Update Issue is the workhorse: resolve, unresolve, or ignore an issue, assign it to a user or a team, and set its priority, changing only the fields you set, with every change reversible by setting the field back. Sentry: Bulk Update Issues applies the same changes to a list of issue ids in one call; always pass ids, because when they are omitted the API applies the change to every issue matching the status filter. Start from ids returned by Sentry: List Project Issues, and use Sentry: Resolve Short ID when all you have is the BACKEND-API-1A form from the UI, a commit message, or a chat link.

Pagination on list nodes

Sentry sends cursors in HTTP Link response headers rather than in the response body, so the list nodes parse them for you and surface a pagination object with next_cursor, prev_cursor, and has_more alongside the data. To fetch the next page, feed pagination.next_cursor into the node's cursor field with otherwise identical parameters, and stop when has_more is false.

Releases and deploys

Sentry: Create Release registers a version for one or more projects so events tag themselves to it and regressions can name the release that reintroduced them; creating an existing version again updates its project associations rather than failing. Sentry: Create Deploy then records where and when it shipped and triggers deploy notifications. One wrinkle worth knowing: deploys cannot be deleted through the API, so a test deploy leaves a harmless permanent record. Sentry: Get Release with health enabled adds crash-free session and user data.

The delete boundary

Sentry: Delete Issue and Sentry: Bulk Delete Issues are the only destructive nodes: they queue permanent, asynchronous removal of an issue group and all its events (the API answers 202 Accepted and deletes in the background), and there is no undo. The bulk node requires an explicit list of issue ids on purpose: the raw API deletes by status filter when ids are omitted, and that project-wide wipe is deliberately not exposed on the canvas. Both need the event:admin scope. Unless the data itself must go, prefer Sentry: Update Issue with status resolved or ignored.

Troubleshooting

Test Connection fails with a 401
The token is invalid, was revoked, or picked up stray whitespace when pasted. One Sentry-specific cause: a User Auth Token stops working when the person who created it leaves the organization, so a credential that worked for months can die with an offboarding. Create a fresh token, or switch to an internal integration token so the credential belongs to the organization, and update the connector.
The token is valid but almost every node returns 403
This is the signature of an Organization Token (Developer Settings > Organization Tokens). Its permissions are fixed for CI release tasks and cannot be customized, so Sentry: Create Release and Sentry: Create Deploy work while issue, event, member, and stats reads are all refused. Create a User Auth Token or an internal integration token with the scopes listed in the credential section and update the connector.
One specific node returns 403 while the rest work
The token is missing that node's scope. The reads mostly need org:read, project:read, team:read, event:read, or member:read; writes need event:write, project:write, or project:releases; the two delete nodes need event:admin. User Auth Token scopes are fixed at creation, so create a new token including the missing scope; internal integration scopes can be edited in place.
A list node returns only part of the data
That is one page. Sentry paginates with cursors carried in Link response headers, which the list nodes surface as a pagination object. Feed pagination.next_cursor into the node's cursor field, keep every other parameter identical, and loop until has_more is false.
The organization exists but nodes report it cannot be found
If the organization lives in Sentry's EU region or on a self-hosted install, the default host is wrong. Set the node's host field to de.sentry.io or your self-hosted domain. Note that the connector-level Test Connection always calls sentry.io, so verify such credentials by running Sentry: List Organizations as a node instead.
An issue id copied from Sentry returns a 404
Ids like BACKEND-API-1A are short IDs, the human-facing form Sentry shows in its UI, commit messages, and chat links; the issue nodes need the numeric issue id. Run Sentry: Resolve Short ID first: it translates the short form into the numeric id and project slug the other nodes take.
Bulk update changed more issues than intended
The ids field was probably left empty. When ids are omitted, the API applies the change to the project's issues matching the status filter, up to its internal bulk limit, so always pass an explicit id list unless a sweeping change is the goal. Also note ids outside the project are silently ignored, so a wrong-project list can look like a partial failure. The typed fields are reversible: run Sentry: Bulk Update Issues again with the same ids and the previous values to walk a mistake back.
A delete node returned 202 but the issue still shows up
Deletion is asynchronous: the API accepts the request and removes the issue group and its events in the background, so a brief lag is normal. Once processed it is permanent, with no undo or recovery endpoint. If the goal was only to get an issue out of the triage view, Sentry: Update Issue with status resolved or ignored does that reversibly.

Sentry is a trademark of its respective owner. Mattering uses platform names to identify the services these integrations connect to; no endorsement or affiliation is implied.

Start Free Explore our Products