Sentry Node

Use the Sentry node to automate Sentry organization, project, team, issue, event, and release operations from a workflow.

Use the Sentry node to automate Sentry organization, project, team, issue, event, and release operations from a workflow.

Credential

Create a Sentry credential with an auth token. Leave Base URL empty for Sentry SaaS, or set the root URL for a self-hosted Sentry instance.

Operations

  • createProject, createRelease, createTeam
  • deleteIssue, deleteProject, deleteRelease, deleteTeam
  • getEvent, getIssue, getProject, getRelease
  • listEvents, listIssues, listOrganizations, listProjects, listReleases, listTeams
  • updateIssue, updateOrganization, updateProject, updateRelease, updateTeam

createIssue and createOrganization are not exposed because Sentry does not document public REST endpoints for them.

Common Fields

FieldDescription
CredentialSentry credential to use
OperationSentry action to run
Organization SlugSentry organization slug for organization update and project, team, issue, event, and release operations
Project SlugProject slug for project get/update/delete and event operations; project slug or ID for issue filters
Team SlugTeam slug for project creation and team update/delete operations
Issue IDIssue ID for issue get/update/delete operations
Event IDEvent ID for event lookup operations
Release VersionRelease version for release get/update/delete operations
NameProject or team name for create operations
SlugOptional project or team slug for create operations
PlatformOptional Sentry platform for project creation
Status / Assigned ToIssue update fields. At least one is required for updateIssue
QuerySentry search query. Omit it for unresolved issues, or set it to an empty string to fetch all issues
LimitResult limit for list operations, capped at 1,000 total results
Release Projects JSONJSON array of project slugs for release creation
Release Refs JSONJSON array of repository/commit objects for release creation
Payload JSONJSON object for update organization, project, release, and team operations

Examples

List unresolved issues:

{
  "sentryOperation": "listIssues",
  "sentryOrganizationSlug": "acme",
  "sentryProjectSlug": "web-app",
  "sentryQuery": "is:unresolved level:error",
  "sentryStatsPeriod": "14d",
  "sentryLimit": "25"
}

Resolve an issue:

{
  "sentryOperation": "updateIssue",
  "sentryOrganizationSlug": "acme",
  "sentryIssueId": "$input.issue_id",
  "sentryStatus": "resolved"
}

Delete an issue:

{
  "sentryOperation": "deleteIssue",
  "sentryOrganizationSlug": "acme",
  "sentryIssueId": "$input.issue_id"
}

Create a release:

{
  "sentryOperation": "createRelease",
  "sentryOrganizationSlug": "acme",
  "sentryReleaseVersion": "web-app@1.2.3",
  "sentryReleaseProjects": "[\"web-app\"]"
}

Update a project:

{
  "sentryOperation": "updateProject",
  "sentryOrganizationSlug": "acme",
  "sentryProjectSlug": "web-app",
  "sentryPayload": "{\"name\":\"Web App\"}"
}

Outputs

List operations return success, operation, count, and the relevant collection such as organizations, projects, teams, issues, events, or releases. Single-resource operations return organization, issue, event, release, project, or team. Delete operations return the relevant resource key with deleted: true and identifying fields.