Skip to main content
Sentry logo
  • Category: developer tools
  • Auth: OAUTH2
  • Composio-managed OAuth available? Yes
  • Tools: 211
  • Triggers: 0
  • Slug: SENTRY
  • Version: 20261101_00

Tools

Slug: SENTRY_ACCESS_PROJECT_INFORMATIONRetrieves detailed information for a Sentry project, given its existing organization and project ID or slug.

Input Parameters

string
required
ID or slug of the Sentry project.
string
required
ID or slug of the Sentry organization to which the project belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_ADD_A_SYMBOL_SOURCE_TO_A_PROJECTTool to add a custom symbol source to a Sentry project. Use when configuring symbol sources for crash symbolication.

Input Parameters

string
Internal ID of the source. Must be distinct and cannot start with ‘sentry:’. UUID generated if not provided.
string
Source URL. Required for HTTP sources.
string
required
Human-readable name of the source.
string ("http" | "gcs" | "s3")
required
Source type. Options: ‘http’ (SymbolServer HTTP), ‘gcs’ (Google Cloud Storage), ‘s3’ (Amazon S3).
string
Bucket name. Required for S3 and GCS sources.
string
S3 or GCS prefix path.
string ("us-east-2" | "us-east-1" | "us-west-1" | "us-west-2" | "ap-east-1" | "ap-south-1" | "ap-northeast-2" | "ap-southeast-1" | "ap-southeast-2" | "ap-northeast-1" | "ca-central-1" | "cn-north-1" | "cn-northwest-1" | "eu-central-1" | "eu-west-1" | "eu-west-2" | "eu-west-3" | "eu-north-1" | "sa-east-1" | "us-gov-east-1" | "us-gov-west-1")
AWS region enumeration for S3 sources.
string
Password for HTTP authentication.
string
Username for HTTP authentication.
string
AWS Access Key. Required for S3 sources.
string
AWS Secret Access Key. Required for S3 sources.
string
GCS private key. Required for GCS sources.
string
GCS email for authentication. Required for GCS sources.
string ("native" | "symstore" | "symstore_index2" | "ssqp" | "unified" | "debuginfod" | "slashsymbols")
required
Layout type specifying the directory structure for symbols. Required for HTTP, GCS, and S3 sources.
string ("default" | "uppercase" | "lowercase")
required
Filename casing convention for symbols. Required for HTTP, GCS, and S3 sources.
array
List of file types to filter.
string
required
The ID or slug of the project.
array
Glob patterns for debug/code file paths.
string
required
The ID or slug of the organization.
boolean
Whether source requires debug checksum. Default: false.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

string
required
The email address of the user to invite or add to the organization.
string ("billing" | "member" | "manager" | "owner" | "admin")
Primary organization-level role. billing: Manages payment/compliance. member: Views events/data. manager: Manages teams, projects, membership. owner: Unrestricted access. admin: Edits global integrations, manages projects/teams. Note: The admin role may have plan-specific restrictions; consider manager or teamRoles.
boolean
If True, resends an invitation to a user previously invited but who has not yet accepted.
array
List of team-specific role assignments. Common roles: contributor (views/acts on issues, may add members per org settings) and admin (full team/project management).
boolean
If True, an invitation email is sent to the user. Set to False to add the member without an email notification.
string
required
The unique identifier (ID or slug) of the Sentry organization to which the member will be added.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_ADD_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.

Input Parameters

string
required
The email address to be added to or removed from the user’s Sentry account. Ensure this is a valid email format.
string
required
The unique identifier of the Sentry user (e.g., numeric ID or ‘self’) for whom the email address is being managed.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_ADD_TEAM_MEMBER_IN_ORGANIZATIONAdds an existing organization member to one of its teams, or may generate an access request when permission to join is needed. An already-existing membership is reported as an error.

Input Parameters

string
required
ID of the existing organization member to be added to the team.
string
required
The ID or slug of the team to which the member will be added. Slugs are typically lowercase and use hyphens.
string
required
The ID or slug of the organization. Slugs are typically lowercase and use hyphens.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_ADD_TEAM_TO_PROJECTGrants a Sentry team access to a Sentry project within the specified Sentry organization.

Input Parameters

string
required
The unique identifier (ID) or human-readable slug for the Sentry team that will be granted access to the project.
string
required
The unique identifier (ID) or human-readable slug for the Sentry project. Access will be granted to this project.
string
required
The unique identifier (ID) or human-readable slug for the Sentry organization. This organization contains both the project and the team.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_BULK_MUTATE_AN_ORGANIZATIONS_ISSUESBulk mutate various attributes on issues within an organization. Use when you need to update status, priority, assignment, or other attributes for multiple issues at once. Maximum of 1000 issues can be mutated, with a 100 issue limit per request.

Input Parameters

array
Issue IDs to mutate. For non-status updates, this parameter is required. For status updates, it can be omitted to update all matching issues.
string ("date" | "new" | "trends" | "freq" | "user" | "inbox")
Sort order for issues. Defaults to ‘date’.
boolean
Mark issue as reviewed in inbox.
integer
Maximum number of issues to affect. Default: 100, Maximum: 100.
boolean
Merge issues together. Requires multiple issue IDs.
string
Search query for filtering issues. Defaults to ‘is:unresolved’ if not specified. Only used when issue IDs are not provided.
string ("resolved" | "unresolved" | "ignored" | "resolvedInNextRelease" | "muted")
New status for the issues.
string
View ID to apply view’s query and filters. Only used when issue IDs are not provided.
boolean
Discard the issues.
boolean
Mark the issue as seen.
array
Project IDs to filter issues by. Use -1 to include all available projects.
boolean
Make the issue public or private.
string ("low" | "medium" | "high")
Priority level for the issue.
string ("archived_until_escalating" | "archived_until_condition_met" | "archived_forever" | "escalating" | "ongoing" | "regressed" | "new")
Issue substatus.
string
User or team to assign the issue to. Formats: <user_id>, user:<user_id>, <username>, <email>, team:<team_id>.
array
Environment names to filter issues by. Used to narrow down which issues to mutate.
boolean
Bookmark or unbookmark the issue.
boolean
Subscribe or unsubscribe from issue notifications.
object
Status details schema for issue resolution.
string
required
The ID or slug of the organization containing the issues to mutate.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_BULK_REMOVE_AN_ORGANIZATIONS_ISSUESPermanently removes issues from an organization. If IDs are provided, queries and filtering are ignored. Maximum of 1000 issues can be removed at once.

Input Parameters

array
The list of issue IDs to be removed. If provided, queries and filtering will be ignored. If not provided, it will attempt to remove the first 1000 issues matching the query and filters.
string
Sort order for issues. Accepts: date, freq, inbox, new, trends, user. Defaults to date if not specified.
integer
The maximum number of issues to affect. The maximum allowed value is 100.
string
An optional search query for filtering issues. A default query will apply if no view/query is set. Only used if issue IDs are not provided.
string
The ID of the view to use. If no query is present, the view’s query and filters will be applied. Only used if issue IDs are not provided.
array
The IDs of projects to filter by. Use -1 to include all available projects.
array
The name of environments to filter by. Used to narrow down which issues to remove based on the environment.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization from which issues will be removed.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_CREATE_AN_ALERT_FOR_AN_ORGANIZATIONCreates a workflow alert for a Sentry organization using the New Monitors and Alerts system. Use when you need to set up automated alerting for issues based on trigger conditions and filters. Note: This endpoint is currently in beta and may change.

Input Parameters

string
required
The name of the alert.
object
required
Configuration for the alert, typically includes ‘frequency’ in minutes. Valid frequency values: 0 (0 min), 5 (5 min), 10 (10 min), 30 (30 min), 60 (1 hour), 180 (3 hours), 720 (12 hours), 1440 (24 hours).
boolean
Whether the alert is enabled or disabled.
object
required
The conditions on which the alert will trigger. Must include ‘logicType’ (one of ‘any-short’, ‘all’, or ‘none’) and ‘conditions’ array. Available trigger conditions: ‘first_seen_event’ (new issue created), ‘issue_resolved_trigger’ (issue resolved), ‘reappeared_event’ (issue reappears), ‘regression_event’ (issue regression). Each condition should have ‘type’, ‘comparison’ (true), and ‘conditionResult’ (true).
string
The name of the environment for the alert to evaluate in.
array
required
The filters to run before the action will fire and the action(s) to fire. Each filter has ‘logicType’ (‘any-short’, ‘all’, or ‘none’), ‘conditions’ array, and ‘actions’ array. Conditions can filter by: level, age_comparison, assigned_to, issue_category, issue_occurrences, issue_priority, event_frequency, tagged_event, event_attribute, latest_release, and more. Actions define what happens when conditions match: email, slack, discord, msteams, pagerduty, opsgenie, jira, github, vsts notifications, or ticket creation.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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 a logical ISO 8601 range.

Input Parameters

string
Optional client-specified unique dashboard identifier; Sentry generates one if omitted.
string
Absolute end datetime (ISO 8601) for time range; ‘start’ must also be set for custom absolute range.
boolean
If true, time range is UTC; otherwise, defaults to user’s local time or organization settings.
string
Absolute start datetime (ISO 8601) for time range; ‘end’ must also be set for custom absolute range.
string
required
Title for the new dashboard.
string
Default relative time range (e.g., ‘24h’, ‘7d’, ‘auto’); ‘auto’ is often 14 days. Overridden if ‘start’ and ‘end’ are provided.
object
Additional key-value filters (Sentry search syntax for keys) for the dashboard.
array
List of widget configurations defining appearance, data queries, and layout.
array
Project IDs to scope dashboard data; if empty/null, may apply to all accessible projects based on org settings.
array
Environment names (e.g., ‘production’) to filter data; if empty/null, all environments included.
string
required
ID or slug of the Sentry organization where the dashboard will be created.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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 must be configured, and external_id is typically required for the external user.

Input Parameters

integer
required
The unique numeric identifier for the external actor linkage being created. Its specific use may depend on the integration or Sentry’s internal handling.
integer
required
The numeric ID of the Sentry user to be linked with the external identity.
string ("github" | "github_enterprise" | "slack" | "gitlab" | "msteams" | "custom_scm")
required
The external identity provider. Allowed values: github, github_enterprise, slack, gitlab, msteams, custom_scm.
string
The user’s unique identifier on the external provider’s platform (e.g., GitHub user ID, Slack member ID). This ID is specific to the selected provider.
string
required
The display name of the user as known on the external provider’s platform (e.g., GitHub username, Slack display name).
integer
required
The numeric ID of the Sentry integration that corresponds to the specified provider and is configured for the organization.
string
required
The unique identifier (ID or slug) of the Sentry organization where the external user linkage will be created.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

string
required
The name for the alert rule. Maximum length of 256 characters.
string
The ID of the Sentry team or user that owns this alert rule. Can be a numeric ID or a string in the format ‘team:<team_id>’ or ‘user:<user_id>’.
string
required
An event search query to filter events for the alert. For example, to include only transactions with status code 400, use http.status_code:400. Use an empty string for no filter.
string
The Sentry dataset this query will execute on. Valid values include events, transactions, metrics, sessions, and generic-metrics. Defaults to events if not specified. Refer to Sentry’s [Metric Alert Rule Types] documentation for valid configurations.
array
required
A list of project slugs to filter by. For metric alerts, this list is typically limited to containing a single project slug.
array
required
List of trigger configurations. Each trigger must specify label (‘critical’ or ‘warning’; ‘critical’ is mandatory), alertThreshold (numeric value to trigger), and actions. Each action specifies type (e.g., ‘email’, ‘slack’, ‘msteams’, ‘pagerduty’, ‘sentry_app’, ‘sentry_notification’, ‘opsgenie’), targetType (must be lowercase, valid values: ‘user’, ‘team’, ‘specific’, ‘sentry_app’), targetIdentifier (ID/name, format varies by type e.g., email string, PagerDuty integer). Optional action fields include inputChannelId (Slack-specific), integrationId (usually required, except for ‘email’/‘sentry_app’), sentryAppId (if action type is ‘sentry_app’), and priority (e.g., PagerDuty ‘critical’, Opsgenie ‘P1’).
string
required
The aggregate function used in this alert rule. Valid functions include count, count_unique, percentage, avg, apdex, failure_rate, p50, p75, p95, p99, p100, and percentile. Refer to Sentry’s [Metric Alert Rule Types] documentation for valid configurations based on dataset and query type.
integer
The type of query. If no value is provided, queryType defaults based on the specified dataset. Supported values: 0 (Error events: event.type:error), 1 (Transaction events: event.type:transaction), 2 (None: for datasets like metrics that don’t use this). See Sentry’s [Metric Alert Rule Types] for valid configurations.
array
A list of event types this alert will relate to. Valid values are default (for events captured via Capture Message), error, and transaction.
integer
required
The time period in minutes to aggregate over. Supported values: 1 (1 minute), 5 (5 minutes), 10 (10 minutes), 15 (15 minutes), 30 (30 minutes), 60 (1 hour), 120 (2 hours), 240 (4 hours), 1440 (24 hours).
string
The name of the environment to filter by. If None or omitted, the alert rule applies to all environments.
integer
Integer representing the monitor type. This determines if the alert rule is actively monitored or monitored based on a specific activation condition. Consult Sentry documentation for specific values and their meanings.
integer
required
The comparison operator for the critical and warning thresholds. 0 for ‘Above’ and 1 for ‘Below’. The resolved threshold uses the opposite operator. For percentage change thresholds, 0 means ‘Higher than’ and 1 means ‘Lower than’.
integer
Optional. The time delta in minutes for the comparison period. Required when using a percentage change threshold (e.g., ‘X% higher/lower compared to comparisonDelta minutes ago’). Cannot be used for Crash Free Session Rate or Crash Free User Rate alerts.
integer
Optional. The numeric value the metric must reach to resolve an active alert. If not provided, it’s automatically set based on the lowest severity trigger’s alertThreshold and thresholdType. For example, if an alert triggers ‘Above’ 50, it might resolve ‘Below’ 50. If thresholdType is 0 (Above), resolveThreshold must typically be less than or equal to the critical threshold; if thresholdType is 1 (Below), it must be greater than or equal.
integer
Optional integer. Represents a trigger condition for when to start monitoring the alert rule, typically used when monitorType indicates conditional monitoring. Consult Sentry documentation for specific values.
string
required
The ID or slug of the organization to which this alert rule belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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, owner, and muting preferences for incidents.

Input Parameters

string
required
The human-readable name for the monitor. This name is used in notifications and the Sentry UI.
string
A unique identifier for the monitor within the organization. If not provided, Sentry will generate one. It must match the pattern ^[a-z][a-z0-9_\-]*$. Changing this slug after creation requires updating any instrumented check-in calls.
string
The Sentry actor ID (team or user) to be designated as the owner of this monitor. Format: ‘user:{user_id}’ or ‘team:{team_id}’. If not provided, the monitor will be unassigned.
object
required
The configuration for the monitor including schedule type, schedule, and timing settings. This is a required field.
string ("active" | "disabled")
The initial status of the monitor. ‘active’ monitors accept check-ins and contribute to quotas, while ‘disabled’ monitors do not. Allowed values: ‘active’, ‘disabled’. Note: Monitors are typically created with ‘disabled’ status by default and must be activated separately.
string
required
The project slug to associate the monitor to. This is a required field.
boolean
A boolean flag to control incident creation for this monitor. If true, monitor incidents (alerts) will be suppressed. Defaults to false if not provided.
string
required
The identifier (ID or slug) of the Sentry organization to which this monitor will belong.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_CREATE_ORGANIZATION_TEAMCreates a new team in a Sentry organization, requiring either a ‘slug’ or ‘name’ to define the team.

Input Parameters

string
Optional. The display name for the new team. If not supplied, it’s auto-generated from the slug (if slug is provided). At least one of name or slug is required to create a team.
string
Optional. A unique, URL-friendly identifier for the new team. If not supplied, it’s auto-generated from the name (if name is provided). Must adhere to the pattern: ^[a-z][a-z0-9_\-]*$.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization where the new team will be created. This organization must already exist.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_CREATE_PROJECT_KEY_WITH_OPTIONAL_RATE_LIMITINGCreates a new client key (DSN) for an existing Sentry project, with optional custom rate limit configuration.

Input Parameters

string
An optional descriptive name for the client key. If not provided, Sentry will generate a default name.
integer
The maximum number of events that can be accepted for this key within the specified rateLimit_window. If omitted, no custom rate limit will be applied to this key.
integer
The time window in seconds for the rateLimit_count. For example, if rateLimit_count is 1000 and rateLimit_window is 3600, the key will accept up to 1000 events per hour. If omitted, no custom rate limit will be applied to this key.
string
required
The unique identifier (ID) or human-readable slug for the Sentry project for which the client key will be created.
string
required
The unique identifier (ID) or human-readable slug for the Sentry organization to which the project belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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 to event patterns for an existing organization and project.

Input Parameters

string
required
Descriptive name for the alert rule.
string
Owner ID (e.g., ‘team:ID’, ‘user:ID’).
array
required
List of action objects executed when conditions (and filters) are met. Each object must specify an ID (action type) and parameters. See examples for required JSON structures: Send a notification to Suggested Assignees - fallthroughType - Who the notification should be sent to if there are no suggested assignees. Valid values are ActiveMembers, AllMembers, and NoOne. json { “id”: “sentry.mail.actions.NotifyEmailAction”, “targetType”: “IssueOwners”, “fallthroughType”: “ActiveMembers” } Send a notification to a Member or a Team - targetType - One of Member or Team. - fallthroughType - Who the notification should be sent to if it cannot be sent to the original target. Valid values are ActiveMembers, AllMembers, and NoOne. - targetIdentifier - The ID of the Member or Team the notification should be sent to. json { “id”: “sentry.mail.actions.NotifyEmailAction”, “targetType”: “Team”, “fallthroughType”: “AllMembers”, “targetIdentifier”: 4524986223 } Send a Slack notification - workspace - The integration ID associated with the Slack workspace. - channel - The name of the channel to send the notification to (e.g., #critical, Jane Schmidt). - channel_id (optional) - The ID of the channel to send the notification to. - tags (optional) - A string of tags to show in the notification, separated by commas (e.g., “environment, user, my_tag”). - notes (optional) - Text to show alongside the notification. To @ a user, include their user id like @<USER_ID>. To include a clickable link, format the link and title like <http://example.com&#124;Click Here>. json { “id”: “sentry.integrations.slack.notify_action.SlackNotifyServiceAction”, “workspace”: 293854098, “channel”: “#warning”, “tags”: “environment,level”, “notes”: “Please <http://example.com&#124;click here> for triage information” } Send a Microsoft Teams notification - team - The integration ID associated with the Microsoft Teams team. - channel - The name of the channel to send the notification to. json { “id”: “sentry.integrations.msteams.notify_action.MsTeamsNotifyServiceAction”, “team”: 23465424, “channel”: “General” } Send a Discord notification - server - The integration ID associated with the Discord server. - channel_id - The ID of the channel to send the notification to. - tags (optional) - A string of tags to show in the notification, separated by commas (e.g., “environment, user, my_tag”). json { “id”: “sentry.integrations.discord.notify_action.DiscordNotifyServiceAction”, “server”: 63408298, “channel_id”: 94732897, “tags”: “browser,user” } Create a Jira Ticket - integration - The integration ID associated with Jira. - project - The ID of the Jira project. - issuetype - The ID of the type of issue that the ticket should be created as. - dynamic_form_fields (optional) - A list of any custom fields you want to include in the ticket as objects. json { “id”: “sentry.integrations.jira.notify_action.JiraCreateTicketAction”, “integration”: 321424, “project”: “349719”, “issueType”: “1” } Create a Jira Server Ticket - integration - The integration ID associated with Jira Server. - project - The ID of the Jira Server project. - issuetype - The ID of the type of issue that the ticket should be created as. - dynamic_form_fields (optional) - A list of any custom fields you want to include in the ticket as objects. json { “id”: “sentry.integrations.jira_server.notify_action.JiraServerCreateTicketAction”, “integration”: 321424, “project”: “349719”, “issueType”: “1” } Create a GitHub Issue - integration - The integration ID associated with GitHub. - repo - The name of the repository to create the issue in. - title - The title of the issue. - body (optional) - The contents of the issue. - assignee (optional) - The GitHub user to assign the issue to. - labels (optional) - A list of labels to assign to the issue. json { “id”: “sentry.integrations.github.notify_action.GitHubCreateTicketAction”, “integration”: 93749, “repo”: “default”, “title”: “My Test Issue”, “assignee”: “Baxter the Hacker”, “labels”: [“bug”, “p1”] } Create a GitHub Enterprise Issue - integration - The integration ID associated with GitHub Enterprise. - repo - The name of the repository to create the issue in. - title - The title of the issue. - body (optional) - The contents of the issue. - assignee (optional) - The GitHub user to assign the issue to. - labels (optional) - A list of labels to assign to the issue. json { “id”: “sentry.integrations.github_enterprise.notify_action.GitHubEnterpriseCreateTicketAction”, “integration”: 93749, “repo”: “default”, “title”: “My Test Issue”, “assignee”: “Baxter the Hacker”, “labels”: [“bug”, “p1”] } } Create an Azure DevOps work item - integration - The integration ID. - project - The ID of the Azure DevOps project. - work_item_type - The type of work item to create. - dynamic_form_fields (optional) - A list of any custom fields you want to include in the work item as objects. json { “id”: “sentry.integrations.vsts.notify_action.AzureDevopsCreateTicketAction”, “integration”: 294838, “project”: “0389485”, “work_item_type”: “Microsoft.VSTS.WorkItemTypes.Task” } Send a PagerDuty notification - account - The integration ID associated with the PagerDuty account. - service - The ID of the service to send the notification to. - severity - The severity of the Pagerduty alert. This is optional, the default is critical for fatal issues, error for error issues, warning for warning issues, and info for info and debug issues. json { “id”: “sentry.integrations.pagerduty.notify_action.PagerDutyNotifyServiceAction”, “account”: 92385907, “service”: 9823924, “severity”: “critical” } Send an Opsgenie notification - account - The integration ID associated with the Opsgenie account. - team - The ID of the Opsgenie team to send the notification to. - priority - The priority of the Opsgenie alert. This is optional, the default is P3. json { “id”: “sentry.integrations.opsgenie.notify_action.OpsgenieNotifyTeamAction”, “account”: 8723897589, “team”: “9438930258-fairy”, “priority”: “P1” } Send a notification to a Sentry app with a custom webhook payload - settings - A list of objects denoting the settings each action will be created with. All required fields must be included. - sentryAppInstallationUuid - The ID for the Sentry app json { “id”: “sentry.rules.actions.notify_event_sentry_app.NotifyEventSentryAppAction”, “settings”: [ {“name”: “title”, “value”: “Team Rocket”}, {“name”: “summary”, “value”: “We’re blasting off again.”} ], “sentryAppInstallationUuid”: “643522”, “hasSchemaFormConfig”: true } Send a notification (for all legacy integrations) json { “id”: “sentry.rules.actions.notify_event.NotifyEventAction” }
array
Optional list of filter objects for additional criteria after conditions are met. Each object must specify an ID (filter type) and parameters. See examples for required JSON structures: The issue is comparison_type than value time - comparison_type - One of older or newer - value - An integer - time - The unit of time. Valid values are minute, hour, day, and week. json { “id”: “sentry.rules.filters.age_comparison.AgeComparisonFilter”, “comparison_type”: “older”, “value”: 3, “time”: “week” } The issue has happened at least value times - value - An integer json { “id”: “sentry.rules.filters.issue_occurrences.IssueOccurrencesFilter”, “value”: 120 } The issue is assigned to No One json { “id”: “sentry.rules.filters.assigned_to.AssignedToFilter”, “targetType”: “Unassigned” } The issue is assigned to targetType - targetType - One of Team or Member - targetIdentifier - The target”s ID json { “id”: “sentry.rules.filters.assigned_to.AssignedToFilter”, “targetType”: “Member”, “targetIdentifier”: 895329789 } The event is from the latest release json { “id”: “sentry.rules.filters.latest_release.LatestReleaseFilter” } The issue”s category is equal to value - value - An integer correlated with a category. Valid values are 1 (Error), 2 (Performance), 3 (Profile), 4 (Cron), and 5 (Replay). json { “id”: “sentry.rules.filters.issue_category.IssueCategoryFilter”, “value”: 2 } The event”s tags match key match value - key - The tag - match - The comparison operator. Valid values are eq (equals), ne (does not equal), sw (starts with), ew (ends with), co (contains), nc (does not contain), is (is set), and ns (is not set). - value - A string. Not required when match is is or ns. json { “id”: “sentry.rules.filters.tagged_event.TaggedEventFilter”, “key”: “level”, “match”: “eq”, “value”: “error” } The event”s level is match level - match - Valid values are eq, gte, and lte. - level - Valid values are 50 (fatal), 40 (error), 30 (warning), 20 (info), 10 (debug), 0 (sample). json { “id”: “sentry.rules.filters.level.LevelFilter”, “match”: “gte”, “level”: “50” }
integer
required
Action performance interval in minutes (5-43200) once conditions are met.
array
required
List of condition objects defining rule triggers. Each object must specify an ID (condition type) and parameters. See examples for required JSON structures: A new issue is created json { “id”: “sentry.rules.conditions.first_seen_event.FirstSeenEventCondition” } The issue changes state from resolved to unresolved json { “id”: “sentry.rules.conditions.regression_event.RegressionEventCondition” } The issue is seen more than value times in interval - value - An integer - interval - Valid values are 1m, 5m, 15m, 1h, 1d, 1w and 30d (m for minutes, h for hours, d for days, and w for weeks). json { “id”: “sentry.rules.conditions.event_frequency.EventFrequencyCondition”, “value”: 500, “interval”: “1h” } The issue is seen by more than value users in interval - value - An integer - interval - Valid values are 1m, 5m, 15m, 1h, 1d, 1w and 30d (m for minutes, h for hours, d for days, and w for weeks). json { “id”: “sentry.rules.conditions.event_frequency.EventUniqueUserFrequencyCondition”, “value”: 1000, “interval”: “15m” } The issue affects more than value percent of sessions in interval - value - A float - interval - Valid values are 5m, 10m, 30m, and 1h (m for minutes, h for hours). json { “id”: “sentry.rules.conditions.event_frequency.EventFrequencyPercentCondition”, “value”: 50.0, “interval”: “10m” }
string ("all" | "any")
required
Logic for condition evaluation: ‘all’ (all conditions must match) or ‘any’ (any condition can match). NOTE: ‘none’ is deprecated and no longer supported.
string
Sentry environment name for event filtering (e.g., ‘production’). If omitted, applies to all environments.
string ("all" | "any" | "none")
Logic for filter evaluation (‘all’, ‘any’, ‘none’) for action execution. Required if ‘filters’ are specified.
string
required
Unique identifier (ID or slug) of the Sentry project for the rule.
string
required
Unique identifier (ID or slug) of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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 enabled.

Input Parameters

string
required
The fully qualified URL to which Sentry will send webhook POST requests for the subscribed events.
array
required
A list of event types to subscribe to for this webhook. Valid event types are: ‘event.alert’ (triggered when alerts fire) and ‘event.created’ (triggered when new events are processed). When any of these events occur in the project, Sentry will send a notification to the specified URL.
string
required
The unique identifier (ID) or human-readable slug of the Sentry project for which to create the webhook.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization to which the project belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_CREATE_RELEASE_DEPLOY_FOR_ORGCreates a new deploy record in Sentry to track the introduction of a release version into a specific environment.

Input Parameters

string
An optional URL that provides a link to the deployment, such as a commit or a CI build page.
string
An optional human-readable name for the deploy.
string
required
The version identifier of the release to be deployed. This version must already exist in Sentry.
array
An optional list of project slugs to associate this deploy with. If not provided, the deploy applies to all projects associated with the release.
string
An optional ISO 8601 formatted date-time string (UTC is recommended) indicating when the deployment process started.
string
required
The name of the environment to which this release is being deployed (e.g., ‘production’, ‘staging’). This environment must be known to Sentry.
string
An optional ISO 8601 formatted date-time string (UTC is recommended) indicating when the deployment process finished. If not provided, Sentry uses the time the deploy API call is received.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_CREATE_RELEASE_FOR_ORGANIZATIONCreates a new Sentry release for an existing organization, associating it with specified projects that must belong to that organization.

Input Parameters

string
An optional commit reference, such as a branch name or a tag. This is useful if a tagged version has been provided (e.g., version is ‘v1.0.0’ and ref is ‘refs/tags/v1.0.0’).
string
An optional URL that points to the release. This can be a link to a GitHub release, a CI build page, or an internal changelog.
array
An optional way to indicate the start and end commits for each repository included in a release. Head commits must include repository and commit (the HEAD SHA). They can optionally include previousCommit (the SHA of the HEAD of the previous release), which should be specified if this is the first time you’ve sent commit data. commit may also contain a range in the form of previousCommit..commit.
array
An optional list of commit data to be associated with the release. Commits must include the id parameter (the SHA of the commit). Optionally, include repository, message, patch_set, author_name, author_email, and timestamp for richer integration and better suspect commit tracking.
string
required
A unique identifier for this release. Can be a semantic version number, a commit hash, or any other string that uniquely identifies this release.
array
required
A list of project slugs that are part of this release. These projects must belong to the specified organization.
string
An optional ISO 8601 timestamp indicating when the release went live. If not provided, the current time is assumed by Sentry.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_CREATE_SCIM_GROUP_FOR_ORGANIZATIONCreates a new Sentry team (SCIM group) within an organization via the SCIM API. Requirements: - Organization must have SCIM enabled (requires Business Plan with SAML2) - Must use a SCIM bearer token (generated when SCIM is enabled) - Token must have ‘team:admin’ or ‘team:write’ scope Behavior: - A URL-friendly slug is auto-generated from displayName (e.g., ‘My Team’ → ‘my-team’) - Team is created with an empty member set - Members must be added separately through SCIM member operations - Returns SCIM 2.0 Group resource with unique ID Use this for SCIM provisioning workflows with identity providers like Okta or Azure AD.

Input Parameters

string
required
Human-readable name for the new team. A URL-friendly slug will be auto-generated by converting to lowercase and replacing spaces with dashes (e.g., ‘My Team’ → ‘my-team’). Must be unique within the organization.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization where the new team will be created. Must be an organization with SCIM enabled.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

string
required
Display name for the new Sentry project.
string
Optional unique identifier for the project (e.g., for URLs), auto-generated from the name if omitted. Pattern: ^[a-z][a-z0-9_\-]*$.
string
Primary platform or language (e.g., python, javascript, java) for SDK setup instructions and issue processing.
boolean
Specifies whether to create default alert rules. If true (API default when parameter is omitted), an alert is triggered for every new issue. If false, no default alerts are created.
string
required
ID or slug of the Sentry team to associate with the project.
string
required
ID or slug of the Sentry organization where the project will be created.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

string
required
User’s email address, used as the SAML identifier for the new member.
string ("billing" | "member" | "manager" | "admin")
Organization role for the new member; defaults to the organization’s default role. The admin role cannot be assigned in Business/Enterprise plans; use TeamRoles instead.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_A_CUSTOM_INTEGRATIONDeletes a custom integration (Sentry App) by its ID or slug. Use when you need to permanently remove a custom integration from your organization. Requires org:admin scope.

Input Parameters

string
required
The ID or slug of the custom integration (Sentry App) to delete. Use the slug (e.g., ‘my-integration’) or UUID. Slugs are case-sensitive.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_AN_ALERT⚠️ This endpoint is currently in beta and may be subject to change. Deletes an alert. Use when you need to permanently remove an alert from an organization.

Input Parameters

integer
required
The ID of the alert you’d like to query.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_BULK_ALERTSBulk delete alerts for a given organization. Use when you need to delete multiple alerts at once. ⚠️ This endpoint is currently in beta and may be subject to change.

Input Parameters

array
The ID of the alert you’d like to delete. Multiple IDs can be provided to delete multiple alerts at once.
string
An optional search query for filtering alerts to delete.
array
The IDs of projects to filter by. ‘-1’ means all available projects. For example: ’/?project=1234&project=56789’ or ’/?project=-1’
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_DSYMS_FOR_PROJECTPermanently removes a specific Debug Information File (DIF), used for symbolicating crash reports, from the specified Sentry project and organization.

Input Parameters

string
required
The unique identifier of the Debug Information File (DIF) to be deleted. This ID is assigned by Sentry when the file is uploaded.
string
required
The unique identifier (ID or slug) of the Sentry project from which the Debug Information File (DIF) will be deleted.
string
required
The unique identifier (ID or slug) of the Sentry organization to which the project belongs. Slugs are short, URL-friendly names.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

string
required
Unique identifier (UUID) of the Sentry app installation.
string
required
Platform-specific identifier of the external issue to be unlinked.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_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.

Input Parameters

string
required
Unique identifier (ID or slug) of the Sentry team.
integer
required
Numeric ID of the external team integration, typically obtained when the link was established.
string
required
Unique identifier (ID or slug) of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_EXTERNAL_USER_FROM_ORGANIZATIONDeletes the link between an external user (from an integration provider like GitHub, Slack, GitLab, or MS Teams) and a Sentry user within the specified organization. This removes the association but does not delete the Sentry user itself. Requires org:admin or org:write permissions.

Input Parameters

integer
required
The unique numerical identifier of the external user linkage to delete. This ID is returned when creating an external user via the ‘create_external_user_for_organization’ action.
string
required
The ID or human-readable slug of the Sentry organization from which to delete the external user link.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

string
required
Identifier (ID) of the organization member to remove from the team (e.g., ‘234567’). Typically a numerical ID.
string
required
Identifier (ID) or slug of the Sentry team from which the member will be removed (e.g., ‘frontend-developers’, ‘98765’). Team slugs are typically lowercase and hyphenated.
string
required
Identifier (ID) or slug of the Sentry organization (e.g., ‘our-company’, ‘123456’). Slugs are typically lowercase and hyphenated.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_ORGANIZATION_ALERT_RULEDeletes a specified Sentry organization metric alert rule. An HTTP 202 response yields an empty result, indicating that the deletion request was accepted for processing.

Input Parameters

integer
required
The numeric ID of the metric alert rule to delete. This ID can be obtained from the alert rule’s URL in the Sentry UI (https://sentry.io/organizations/&#123;org&#125;/alerts/rules/details/&#123;alert_rule_id&#125;/) or by listing alert rules via the API. Note: Metric alert rules require a Business or Enterprise Sentry plan.
string
required
The ID or slug of the organization. The organization slug is a URL-friendly name (e.g., ‘my-organization’), while the ID is a numeric string. You can find this in your Sentry organization settings URL: https://sentry.io/settings/&#123;organization_slug&#125;/

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_ORGANIZATION_DASHBOARDDeletes a custom dashboard or tombstones (marks as deleted) a pre-built dashboard within a Sentry organization.

Input Parameters

integer
required
Numerical ID of the dashboard to delete.
string
required
Identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_ORGANIZATION_DISCOVER_QUERYPermanently removes a specific saved Discover query (a configuration for exploring event data) from a Sentry organization. This action requires one of the following scopes: org:admin, org:read, or org:write. The Discover saved queries feature is only available on Business and Enterprise plans.

Input Parameters

integer
required
The unique integer identifier of the saved Discover query that you intend to delete.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization to which the Discover query belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_ORGANIZATION_INTEGRATIONPermanently removes an integration installation from a Sentry organization. This action requires the numeric integration ID, which can be obtained by first calling retrieve_organization_integrations_list. Required permissions: org:admin or org:integrations scope.

Input Parameters

string
required
The numeric ID of the integration installation on the organization. This is a string representation of a numeric value (e.g., ‘12345’, ‘67890’). You can obtain integration IDs by first listing the organization’s integrations using the retrieve_organization_integrations_list action.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization from which the integration will be deleted.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_ORGANIZATION_ISSUEPermanently deletes a specific Sentry issue, identified by its ID, from an organization; this operation is irreversible and idempotent.

Input Parameters

string
required
The unique identifier (ID) of the Sentry issue to be permanently deleted.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization to which the issue belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_ORGANIZATION_MEMBERPermanently removes a member from a Sentry organization, revoking their access to that organization and all its associated projects.

Input Parameters

string
required
The unique identifier (ID) of the member to be removed from the organization.
string
required
The unique identifier (ID) or the human-readable slug of the Sentry organization from which the member will be removed.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_ORGANIZATION_MONITORDeletes a Sentry cron monitor or, if environment is specified, only specific environments within that monitor.

Input Parameters

array
Optional list of environment names to delete; if omitted, the entire monitor (including all its environments) is deleted.
string
required
The ID or slug of the Sentry cron monitor to be deleted.
string
required
The ID or slug of the Sentry organization to which the monitor belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_ORGANIZATION_RELEASEPermanently and irreversibly removes a Sentry release, including all its associated files, identified by its version from the specified organization.

Input Parameters

string
required
The version identifier of the release to be deleted. This could be a semantic version (e.g., ‘1.0.0’, ‘my-app@2.3.1’) or a unique commit hash.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization to which the release belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_ORGANIZATION_RELEASE_FILETool to delete a file from an organization release. Use when you need to remove a specific file associated with a release version in an organization.

Input Parameters

string
required
The ID of the file to delete.
string
required
The version identifier of the release.
string
required
The ID or slug of the organization the release belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

integer
required
The unique numerical identifier (ID) of the notification action to be deleted.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_PROJECT_BY_IDSchedules a Sentry project for asynchronous deletion within a specified organization, hiding it from most public views once the process begins.

Input Parameters

string
required
The unique identifier (ID) or URL-friendly slug of the Sentry project to be deleted.
string
required
The unique identifier (ID) or URL-friendly slug of the Sentry organization to which the project belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_PROJECT_HOOKDeletes a specific service hook from a Sentry project using its organization, project, and hook identifiers.

Input Parameters

string
required
The unique identifier (GUID) of the service hook to be deleted from the specified project.
string
required
The unique identifier (ID) or human-readable slug of the Sentry project from which the service hook will be removed.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization to which the project and service hook belong.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_PROJECT_ISSUESPermanently removes specified issues from a Sentry project; if no issue IDs are provided, it removes the oldest 1000 issues.

Input Parameters

array
A list of specific issue IDs to be permanently removed. If not provided, the action removes the oldest 1000 issues in the project.
string
required
The unique identifier (ID or slug) of the Sentry project from which issues will be removed.
string
required
The unique identifier (ID or slug) of the Sentry organization to which the project and its issues belong.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_PROJECT_KEYPermanently deletes a specific client key (DSN) for a project, preventing it from being used to send events to Sentry.

Input Parameters

string
required
The ID of the client key (public DSN key) to delete.
string
required
The ID or slug of the project to which the client key belongs.
string
required
The ID or slug of the organization to which the project belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_PROJECT_MONITORDeletes a Sentry monitor, or optionally only its specified environments, for a given project.

Input Parameters

array
Optional. A list of environment names. If provided, only the monitor configurations for these specific environments will be deleted. If this parameter is omitted or an empty list is passed, the entire monitor and all its environment configurations will be deleted.
string
required
The unique identifier (ID or slug) of the Sentry monitor to be deleted.
string
required
The unique identifier (ID or slug) of the Sentry project to which the monitor belongs.
string
required
The unique identifier (ID or slug) of the Sentry organization to which the project and monitor belong.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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 organization.

Input Parameters

string
required
The unique identifier (ID) of the session replay to be deleted.
string
required
The unique identifier (ID) or human-readable slug for the Sentry project from which the replay will be deleted.
string
required
The unique identifier (ID) or human-readable slug for the Sentry organization to which the project and replay belong.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_PROJECT_RULEPermanently deletes a specific issue alert rule from an existing project within an existing Sentry organization.

Input Parameters

integer
required
The numerical ID of the specific issue alert rule that needs to be deleted from the project.
string
required
The unique identifier (ID or slug) of the Sentry project from which the alert rule will be deleted. Slugs are typically lowercase and hyphenated (e.g., ‘my-web-project’).
string
required
The unique identifier (ID or slug) of the Sentry organization that contains the project and the alert rule to be deleted. Slugs are typically lowercase and hyphenated (e.g., ‘my-sentry-org’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_PROJECT_TEAM_ASSOCIATIONRevokes a team’s access to a Sentry project; this operation is idempotent.

Input Parameters

string
required
The unique identifier (ID) or human-readable slug of the Sentry team to be disassociated from the project.
string
required
The unique identifier (ID) or human-readable slug of the Sentry project.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_RELEASE_FILE_BY_IDPermanently deletes a specific build artifact (e.g., source map, application bundle) associated with a project release.

Input Parameters

string
required
The numeric ID of the specific file to be deleted from the release. This ID is returned when a file is uploaded or can be retrieved by listing release files.
string
required
The version identifier of the release from which the file will be deleted. This can be a semantic version, a commit hash, or any unique string identifying the release.
string
required
The unique identifier (ID or slug) of the Sentry project to which the release belongs.
string
required
The unique identifier (ID or slug) of the Sentry organization to which the release belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_SYMBOL_SOURCE_FROM_PROJECTDeletes a custom symbol source from a Sentry project. Use when you need to remove a symbol source that is no longer needed or needs to be reconfigured.

Input Parameters

string
required
The ID of the symbol source to delete.
string
required
The ID or slug of the project containing the symbol source.
string
required
The ID or slug of the organization the project belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_TEAM_BY_ORGANIZATION_OR_TEAM_SLUGSchedules a Sentry team for asynchronous deletion, which releases the team’s slug for reuse upon successful scheduling.

Input Parameters

string
required
The unique identifier (ID) or URL-friendly slug of the Sentry team targeted for deletion. For example, ‘frontend-devs’ or ‘67890’.
string
required
The unique identifier (ID) or URL-friendly slug of the Sentry organization to which the team belongs. For example, ‘acme-corp’ or ‘12345’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_TEAM_FROM_ORG_SCIM_V2Permanently and irreversibly deletes a specific team from a Sentry organization via a SCIM v2 request, provided SCIM integration is enabled for the organization.

Input Parameters

string
required
The ID or slug of the team to be deleted. Can be either a numeric ID (as string) or a team slug.
string
required
The ID or URL-friendly slug of the Sentry organization from which the team will be deleted.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_USER_EMAILS_BY_IDRemoves a specified email address from a Sentry user’s account.

Input Parameters

string
required
The email address to remove from the user’s Sentry account. Must be a secondary email (not the primary email).
string
required
Unique identifier of the Sentry user. Use ‘me’ for the currently authenticated user.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DELETE_USER_FROM_ORGRemoves a SCIM-managed member from a Sentry organization that has SCIM enabled, permanently revoking their access.

Input Parameters

string
required
The unique identifier of the organization member to remove.
string
required
The identifier or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_DISABLE_SPIKE_PROTECTIONDisables Spike Protection feature for specified projects within a Sentry organization. Use this when you need to turn off spike protection for one or more projects.

Input Parameters

array
required
List of project slugs to disable Spike Protection for; use ['$all'] to disable for all projects in the organization.
string
required
The unique identifier (ID) or URL-friendly slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_FETCH_ALERTSRetrieves a list of alerts (workflows) for a Sentry organization. Use to get alert configurations, statuses, and trigger details. ⚠️ Note: This endpoint is currently in beta and may be subject to change. It is supported by New Monitors and Alerts and may not be viewable in the UI today.

Input Parameters

array
The ID of the alert you’d like to query. Can specify multiple IDs.
string
An optional search query for filtering alerts.
string
The field to sort results by. If not specified, the results are sorted by id. Available fields are: name, id, dateCreated, dateUpdated, connectedDetectors, actions, priorityDetector. Prefix with - to sort in descending order (e.g., -dateCreated).
array
The IDs of projects to filter by. Use [-1] to include all available projects. For example: [1234, 56789] or [-1].
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_FETCH_A_MONITORFetches detailed information for a specific monitor (detector) within an organization. Use when you need to retrieve monitor configuration, status, or settings. This endpoint is currently in beta and is supported by New Monitors and Alerts.

Input Parameters

integer
required
The ID of the monitor you’d like to query.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_FETCH_AN_ALERTRetrieves detailed information for a specific alert workflow. Use when you need to get alert configuration, triggers, action filters, or monitoring status. This endpoint is currently in beta and supported by New Monitors and Alerts.

Input Parameters

integer
required
The ID of the alert you’d like to query.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_FETCH_AN_ORGANIZATIONS_MONITORSRetrieves monitors (detectors) for a Sentry organization. This endpoint is currently in beta and may be subject to change. Use when you need to list or query monitors for an organization.

Input Parameters

array
The ID of the monitor you’d like to query. Can specify multiple monitor IDs to filter by.
string
An optional search query for filtering monitors.
string
The property to sort results by. If not specified, results are sorted by id. Available fields: name, id, type, connectedWorkflows, latestGroup, openIssues. Prefix with - to sort in descending order.
array
The IDs of projects to filter by. Use -1 to include all available projects. Can specify multiple project IDs.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_FETCH_ISSUE_EVENT_BY_IDRetrieves the ‘latest’, ‘oldest’, or ‘recommended’ event for a Sentry issue within an organization, optionally filtered by environment(s).

Input Parameters

string
required
The event to retrieve. Use ‘latest’ for most recent, ‘oldest’ for first, ‘recommended’ for Sentry’s recommended event, or a specific event ID.
integer
required
The unique numerical ID of the Sentry issue for which to fetch an event.
array
Filter by environment names; if omitted, events from all environments are considered.
string
required
The ID or slug of the organization the issue belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_FETCH_ORGANIZATION_ALERT_RULESRetrieves metric alert rules for a Sentry organization by ID or slug. A 404 with the detail “The requested resource does not exist” is returned as an empty list, which does not by itself establish that the organization has no rules.

Input Parameters

string
required
The unique identifier (ID) or human-readable slug of the Sentry organization for which alert rules are to be fetched. Slugs are typically the organization’s name in lowercase, using hyphens for spaces (e.g., ‘acme-corp’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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 times must be provided together. [WARNING]: This API is experimental (Alpha) and subject to change!

Input Parameters

string
required
The inclusive end of the time series range for querying release threshold statuses. Must be in UTC ISO8601 format (e.g., ‘2023-01-01T23:59:59Z’).
string
required
The start of the time series range for querying release threshold statuses. Must be in UTC ISO8601 format (e.g., ‘2023-01-01T00:00:00Z’).
array
A list of release versions (e.g., ‘1.0.0’, ‘my-app@2.1.3’) to filter the release threshold statuses by. If not provided, statuses for all releases within the time range are considered.
array
A list of environment names (e.g., ‘production’, ‘staging’) to filter the release threshold statuses by. If not provided, statuses for all environments are considered.
array
A list of project slugs (e.g., ‘frontend’, ‘backend-api’) to filter the release threshold statuses by. If not provided, statuses for all projects in the organization are considered.
string
required
The ID or slug of the Sentry organization for which to fetch release threshold statuses.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_FETCH_ORGANIZATION_REPLAY_COUNTRetrieves the total count of session replays for a specified Sentry organization, filterable by time range, environment, project, and query.

Input Parameters

string
The end timestamp for the query period, in ISO-8601 format (e.g., 2001-12-14T12:34:56.7890Z).
string
A Sentry search query string to further filter replays. Example: (transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def). Refer to Sentry documentation for detailed query syntax.
string
The start timestamp for the query period, in ISO-8601 format (e.g., 2001-12-14T12:34:56.7890Z).
array
A list of project IDs to filter results by. Use [-1] to include all available projects within the organization.
array
A list of environment names to filter results by (e.g., production, staging).
string
A relative time period for the query, which overrides start and end if provided. Format is a number followed by d (days), h (hours), m (minutes), s (seconds), or w (weeks). For example, 24h queries data from the last 24 hours.
string
required
The unique identifier (ID or slug) of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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 refining by projects, environments, or specific fields.

Input Parameters

string
Inclusive end of the time series range (UTC ISO8601 or epoch seconds). Use with start; alternative to statsPeriod.
string
Field to sort replay details by (prefix with ’-’ for descending, e.g., ‘-started_at’).
array
Specific fields to include in the response (e.g., ‘activity’, ‘browser’). See FieldEnm for valid fields.
string
Structured query string to filter replay details (e.g., user.email:test@example.com, has:error).
string
Start of the time series range (UTC ISO8601 or epoch seconds). Use with end; alternative to statsPeriod.
string
Pagination cursor for fetching the next or previous set of results.
array
List of project IDs to filter replay details by.
integer
Maximum number of items to return per page for pagination.
string
required
ID of the specific replay session to retrieve.
string
Environment (e.g., ‘production’, ‘staging’) to filter replay details by.
string
Time range for series data, relative to now (e.g., 1d, 2h). Use if not providing start and end.
string
required
ID or slug of the Sentry organization for the replay.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_FETCH_ORGANIZATION_REPLAY_SELECTORSRetrieves replay selectors (CSS/DOM selectors from session replays) for a Sentry organization. Selectors include elements with dead clicks or rage clicks, useful for identifying UI issues. Returns selector details with click counts and associated project IDs. Use statsPeriod for time filtering (preferred over start/end).

Input Parameters

string
End of time range (UTC ISO8601 or epoch seconds). Use with start; not with statsPeriod. Note: This endpoint may not support start/end parameters - prefer using statsPeriod instead.
string
Field to sort replay selectors by. Refer to Sentry API docs for available fields.
string
Sentry search query syntax for filtering. See Sentry docs for syntax/fields.
string
Start of time range (UTC ISO8601 or epoch seconds). Use with end; not with statsPeriod. Note: This endpoint may not support start/end parameters - prefer using statsPeriod instead.
string
Pagination cursor for fetching next/previous page.
array
Filter by project IDs (numeric).
integer
Maximum items per page (API defaults to 100 if not specified, max 100).
array
Filter by environment names.
string
Time range (e.g., 1d, 2h; m, h, d, w units). Use instead of start/end.
string
required
ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_FETCH_PROJECT_ENVIRONMENT_DETAILSRetrieves detailed information for a specific environment within a Sentry project.

Input Parameters

string
required
The name of the environment (e.g., production, staging, development).
string
required
The ID or slug of the Sentry project.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_FETCH_PROJECT_OWNERSHIP_DETAILSRetrieves the ownership configuration, like CODEOWNERS rules or Issue Owner settings, for a specified Sentry project.

Input Parameters

string
required
The unique identifier (ID) or human-readable slug of the Sentry project for which ownership details are to be retrieved. This is used as a path parameter in the API request.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization to which the project belongs. This is used as a path parameter in the API request.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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 version with associated files.

Input Parameters

string
required
The version identifier of the release (e.g., ‘1.0.0’, ‘my-app@2.3.12’).
string
required
The unique identifier (ID) or human-readable slug of the project.
string
required
The unique identifier (ID) or human-readable slug of the organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_FETCH_PROJECT_REPLAY_CLICKSFetches a list of user click interactions for a specific Sentry session replay, including the clicked DOM element ID and timestamp.

Input Parameters

string
Sentry search query to filter click events (e.g., (transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def)).
string
Pagination cursor to navigate through click events.
integer
Maximum number of click events per page (default/max 100).
string
required
The ID of the Sentry session replay.
array
List of environment names to filter click data.
string
required
The ID or slug of the Sentry project.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_FETCH_REPLAY_RECORDING_SEGMENTRetrieves a specific recording segment for a Sentry replay, requiring valid organization, project, replay, and segment identifiers.

Input Parameters

string
required
The unique identifier of the replay to retrieve. This is a 32-character hexadecimal string (UUID4) without dashes. Example: “a6ef355da2bb43f8a7825c45f98c5177”.
integer
required
The ID of the specific recording segment within the replay to retrieve. Segment IDs start from 0 and increment sequentially.
string
required
The ID or slug of the project to which the replay belongs. Examples: ‘javascript’, ‘my-project’.
string
required
The ID or slug of the organization to which the replay belongs. Examples: ‘sentry’, ‘my-org’.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_FETCH_TAG_VALUES_FOR_ISSUERetrieves a list of distinct values for a specified tag key associated with an existing Sentry issue, useful for understanding tag manifestations like browser versions or affected users.

Input Parameters

string
required
The specific tag key (e.g., ‘browser’, ‘user_id’, ‘environment’) for which to retrieve distinct values associated with the issue.
string ("age" | "count" | "date" | "id")
Sort order for tag values; valid options are ‘age’, ‘count’, ‘date’, ‘id’. Prefix with ’-’ for descending (e.g., ‘-count’); defaults to ‘-id’.
integer
required
The unique numerical identifier of the Sentry issue for which tag values are to be fetched.
array
A list of environment names to filter the tag values; if provided, only values from these specified environments will be returned.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_ACTIVATION_OF_ALERT_RULE_FOR_ORGANIZATIONThis legacy operation retrieved activations for a specific metric alert rule in a Sentry organization, allowing users to review the rule’s activations. DEPRECATED: Activation data is unavailable through this action.

Input Parameters

integer
required
The numeric identifier of the metric alert rule whose activations are to be retrieved.
string
required
The unique identifier (ID) or slug of the Sentry organization to which the alert rule belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_ALERTSTool to retrieve all combined alert rules and monitors for a Sentry organization. Use when you need to get a unified view of both alert rules and cron monitors. This endpoint combines results from multiple sources into a single response.

Input Parameters

array
Sort fields for ordering results. Common values include ‘incident_status’, ‘date_triggered’, ‘name’.
array
Filter by team slugs. Use ‘unassigned’ to filter for rules with no team assigned.
array
Expand related data in the response. Can include ‘latestIncident’ to get latest incident details and ‘lastTriggered’ for last trigger timestamp.
string
required
The organization slug or ID to fetch alerts for.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

string
required
The unique numeric ID of the integration installed for the specified organization. This is the integration’s internal ID (e.g., ‘12345’), not the provider key. To find integration IDs, use the list organization integrations endpoint.
string
required
The Sentry organization’s unique ID or human-readable slug (e.g., ‘the-acme-corp’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_OLDEST_EVENTRetrieves the oldest (first) event associated with a Sentry issue within an organization. Use this action when you need to investigate the original occurrence of an issue to understand its root cause or initial context. This is particularly useful for debugging issues from their first appearance, analyzing initial error conditions, or determining when a problem first started occurring.

Input Parameters

integer
required
The unique numerical ID of the Sentry issue for which to retrieve the oldest event.
array
Filter by environment names; if omitted, events from all environments are considered.
string
required
The ID or slug of the organization the issue belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

string
Optional query parameter controlling response detail level. Set to “0” to exclude project and team details for a more concise response. Set to “1” (or omit entirely) for full details including projects and teams.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

boolean
Set to true to list only organizations where the authenticated user is an owner.
string
Filter results using Sentry’s query syntax. Supported fields: id (organization ID), slug (organization slug), status (current status like ‘active’, ‘pending_deletion’), email or member_id (member’s email or ID), platform (project platform like ‘python’), and query (substring match on organization name, slug, member details).
string
Opaque cursor for pagination to retrieve next/previous result sets.
string
Sort results by ‘members’ (number of members), ‘projects’ (number of projects), or ‘events’ (number of events in past 24h), in descending order. Defaults to creation date.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_ORGANIZATION_ENVIRONMENTSLists deployment environments for a Sentry organization, optionally filtered by visibility status. Environments represent deployment contexts like ‘production’, ‘staging’, or ‘development’ where events are tracked. By default, only visible environments are returned. Use the visibility parameter to include hidden environments or view only hidden ones.

Input Parameters

string ("all" | "hidden" | "visible")
Filter by visibility status. Options: ‘visible’ (default, shows only visible environments), ‘hidden’ (shows only hidden environments), ‘all’ (shows all environments including hidden).
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_ORGANIZATION_ISSUE_DETAILSRetrieves detailed information for a specific issue within a Sentry organization. Accepts both numeric issue IDs (e.g., ‘7159174717’) and short IDs displayed in the Sentry UI (e.g., ‘PROJECT-123’, ‘SENTRY-4V’). Short IDs are automatically resolved to numeric IDs before fetching issue details.

Input Parameters

string
required
The issue ID. Can be either a numeric ID (e.g., ‘7159174717’) or a short ID displayed in the Sentry UI (e.g., ‘PROJECT-123’, ‘SENTRY-4V’). Short IDs will be automatically resolved to numeric IDs.
string
required
The unique identifier (ID) or URL-friendly slug of the Sentry organization to which the issue belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_ORGANIZATION_RELEASE_VERSIONRetrieves detailed information, including optional health data and statistics, for a specific release version within a Sentry organization.

Input Parameters

string ("crash_free_sessions" | "crash_free_users" | "date" | "sessions" | "users")
Enumeration of fields for sorting release-related data.
string
Filter data for this release using Sentry’s search syntax (e.g., to find specific events). See Sentry documentation for syntax. Example from Sentry: '''(transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def)'''
boolean
Include health data (e.g., crash rates, session statistics) with release details.
string ("archived" | "open")
Enumeration of release statuses.
string
required
The unique version identifier of the release. This can be a semantic version (e.g., ‘1.2.3’), a commit hash, or any string used to identify the release (e.g., ‘backend@1.0.0-alpha’).
string
ID of a specific project to scope release details; if omitted, details may cover multiple projects.
boolean
Include information about the release’s adoption stages.
string ("14d" | "1d" | "1h" | "24h" | "2d" | "30d" | "48h" | "7d" | "90d")
Enumeration of time periods for release health statistics.
string ("14d" | "1d" | "1h" | "24h" | "2d" | "30d" | "48h" | "7d" | "90d")
Enumeration of time periods for release summary statistics.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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 12, 2023, results are capped at 10,000 data points, statsPeriod overrides start/end timestamps, and the interval parameter (default/min ‘1h’, max ‘1d’, format like statsPeriod) dictates time series resolution and must cleanly divide one day.

Input Parameters

string
End of the query period (ISO-8601 format). Ignored if statsPeriod is provided.
array
required
Fields for session statistics (e.g., sum(session), count_unique(user), p99(session.duration), crash_free_rate(user)). Session duration aggregations may be incomplete for data after Jan 12, 2023.
string
Sentry search query to filter sessions (e.g., (transaction:foo AND release:abc)). See Sentry docs for syntax.
string
Start of the query period (ISO-8601 format). Ignored if statsPeriod is provided.
array
Properties to group session data by (e.g., project, release, environment, session.status).
string
Field from field parameter to order results by. Prefix with ’-’ for descending (e.g., -sum(session)).
array
Project IDs to filter sessions by. Use [-1] for all accessible projects.
string
Time series data resolution (e.g., ‘1h’, ‘1d’; format like statsPeriod). Minimum ‘1h’, maximum ‘1d’. Must cleanly divide one day.
integer
Maximum number of groups (aggregated data points based on groupBy) per request.
array
Environment names to filter sessions by (e.g., ‘production’, ‘staging’).
string
Relative query period (e.g., ‘24h’, ‘7d’), overrides start and end. Uses ‘d’ (days), ‘h’ (hours), ‘m’ (minutes), ‘s’ (seconds), or ‘w’ (weeks).
integer
Set to 0 to exclude, 1 (API default) to include time series data.
integer
Set to 0 to exclude, 1 (API default) to include totals.
string
required
Unique ID or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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 resolution, with filtering by project, category, and outcome.

Input Parameters

string
Inclusive end of the time series range (UTC ISO8601 datetime string or Unix timestamp). Use with start instead of statsPeriod.
string ("sum(quantity)" | "sum(times_seen)")
required
Aggregation field for event counts. Interpretation depends on event type: sum(quantity): For attachments, total size in bytes. For sessions, total events within sessions. For others, event count. sum(times_seen): Sum of unique occurrences. For sessions, count of unique sessions. For attachments, total attachments.
string
Start of the time series range (UTC ISO8601 datetime string or Unix timestamp). Use with end instead of statsPeriod.
string
Reason an event was filtered or dropped (e.g., project_quota, invalid_origin).
string ("accepted" | "filtered" | "rate_limited" | "invalid" | "abuse" | "client_discard" | "cardinality_limited")
Filter by event outcome status (e.g., accepted, filtered, rate-limited).
array
List of project IDs (strings or integers) to filter by. Omit or use empty list for all projects.
string ("error" | "transaction" | "attachment" | "replays" | "profiles")
Filter by event category. If ‘attachment’, other categories cannot be included. If ‘error’, default and security are also included.
boolean
If true, triggers a CSV download of the response; otherwise JSON.
string
Time series resolution (e.g., 1h). Default is 1h. Minimum 1h. Intervals must cleanly divide one day and cannot exceed 1d.
string
Relative time series range (e.g., 1d, 2h). Units: m, h, d, w. Use instead of start and end. Defaults to 24h if no time range is specified.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_PROJECT_EVENTSRetrieves a list of error events for a specified project within a Sentry organization, with options for pagination and detail level.

Input Parameters

string
End of the query period in ISO-8601 format. Must be used with ‘start’ parameter. Cannot be used with ‘statsPeriod’ parameter.
boolean
If True, retrieves full event details including stacktraces; otherwise, a summary is returned.
string
Beginning of the query period in ISO-8601 format. Must be used with ‘end’ parameter. Cannot be used with ‘statsPeriod’ parameter.
string
Opaque cursor for pagination, pointing to the start of the next/previous page, typically from a ‘Link’ header.
boolean
If True, returns events in a pseudo-random yet deterministic order.
string
Time range for events in format: number + unit (d=days, h=hours, m=minutes, s=seconds, w=weeks). Cannot be used with ‘start’ and ‘end’ parameters.
string
required
The ID or slug of the Sentry project.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_PROJECT_EVENT_STATSRetrieves time-series event statistics for a Sentry project. Returns an array of [timestamp, count] data points showing event volumes over time. Use this to analyze event trends, monitor error rates, or generate custom dashboards. The endpoint supports different event types (received, rejected, blacklisted, generated) and time resolutions (10s, 1h, 1d). Important: This endpoint may change in the future without notice. Monitor Sentry’s API changelog for updates. Common use cases: - Monitor error rates over time - Analyze event rejection patterns - Generate custom analytics dashboards - Track event volume trends

Input Parameters

string ("received" | "rejected" | "blacklisted" | "generated")
The type of event statistic to retrieve: ‘received’ (events accepted by Sentry), ‘rejected’ (events rejected due to rate limits/filters), ‘blacklisted’ (events from blocked sources), or ‘generated’ (events created by Sentry). If not specified, defaults to ‘received’.
string
UNIX timestamp (seconds since epoch) marking the start of the query period. Must be earlier than ‘until’ if both are provided. If not specified, defaults to 24 hours before the current time.
string
UNIX timestamp (seconds since epoch) marking the end of the query period. Must be later than ‘since’ if both are provided. If not specified, defaults to the current time.
string ("10s" | "1h" | "1d")
Time granularity for data aggregation: ’10s’ (10-second intervals), ‘1h’ (hourly intervals), or ‘1d’ (daily intervals). Finer resolutions (10s) return more data points but may be slower. If not specified, Sentry automatically selects an appropriate resolution based on the time range.
string
required
The unique identifier (ID) or human-readable slug of the project.
string
required
The unique identifier (ID) or human-readable slug of the organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_PROJECT_HOOKRetrieves detailed information for an existing service hook within a Sentry project. Service hooks (webhooks) are HTTP callbacks that notify external systems when specific events occur in Sentry, such as when alerts are triggered (‘event.alert’) or new events are processed (‘event.created’). This action requires: - Authentication with ‘project:read’ scope - The hook_id (GUID) of an existing service hook, typically obtained from creating a hook or listing project hooks Common use cases: - Verifying hook configuration and status - Retrieving the webhook URL and secret for external system setup - Checking which events the hook is subscribed to - Auditing hook creation timestamps Note: The ‘servicehooks’ feature must be enabled on your Sentry plan to create or manage hooks, though reading existing hook details may be possible depending on your API permissions.

Input Parameters

string
required
The unique identifier (GUID) of the service hook to be retrieved. This ID is assigned when the hook is created.
string
required
The unique identifier (ID) or URL-friendly slug of the Sentry project to which the service hook is bound.
string
required
The unique identifier (ID) or URL-friendly slug of the Sentry organization to which the project and its service hook belong.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_PROJECT_LISTLists all Sentry projects the authenticated token has membership access to across all organizations. IMPORTANT: This endpoint returns projects where the token’s user is a member. An empty result does NOT mean no projects exist - it means the token lacks project membership. This commonly happens when: - The auth token has organization-level access but not explicit project membership - Projects exist in organizations you can access, but you’re not a project member If you receive an empty list but know projects exist, use SENTRY_RETRIEVE_ORGANIZATION_PROJECTS instead, which lists all projects within a specific organization (requires organization_id_or_slug parameter).

Input Parameters

string
Opaque cursor for paginating through project lists, typically obtained from pagination details in a previous API response.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_PROJECT_MONITOR_BY_IDRetrieves detailed information for a specific Sentry cron monitor, provided the organization, project, and monitor exist.

Input Parameters

string
required
ID or slug of the Sentry cron monitor.
string
required
ID or slug of the Sentry project.
string
required
ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_PROJECT_RULE_DETAILSRetrieves detailed information for a specific issue alert rule within a Sentry project.

Input Parameters

integer
required
ID of the alert rule.
string
required
ID or slug of the Sentry project.
string
required
ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_SCIM_GROUP_BY_TEAM_IDRetrieves SCIM group information for a specific Sentry team. Returns the team’s SCIM representation including ID, display name, and member list (limited to 10,000 members). Requires SCIM to be enabled for the organization (Business Plan with SAML2). Use this to query team details via the SCIM protocol for identity provider integrations.

Input Parameters

string
required
The ID or slug of the Sentry team to query. Can be either a numeric team ID (e.g., ‘4508539392294912’) or a team slug (e.g., ‘backend-team’).
string
required
The slug or numeric ID of the Sentry organization that owns the team. SCIM must be enabled for this organization (requires Business Plan with SAML2).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_SENTRY_APP_INSTALLATIONS_FOR_ORGANIZATIONRetrieves a list of Sentry App installations for a given organization, which must exist.

Input Parameters

string
required
The ID or slug of the organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_TEAM_MEMBERS_BY_ID_OR_SLUGRetrieves a page of Sentry team members with user information, organization and team roles, authentication status, and membership flags. Supports pagination with a cursor.

Input Parameters

string
Optional pagination cursor for fetching the next page of results. Obtain this value from the ‘Link’ header in the previous API response. Leave empty for the first request.
string
required
The ID or slug of the team. Can be either a numeric ID (e.g., ‘4510810786627585’) or a URL-friendly slug (e.g., ‘backend-team’).
string
required
The ID or slug of the organization. Can be either a numeric ID (e.g., ‘4508539392294912’) or a URL-friendly slug (e.g., ‘my-organization’).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_GET_WHO_VIEWED_REPLAY_BY_PROJECTRetrieves users who viewed a session replay in a Sentry project and organization. An empty list can also indicate a 404 response or a successful response without a usable nested viewer list, rather than proving that nobody viewed the replay.

Input Parameters

string
required
The unique identifier of the session replay. This is a 32-character hexadecimal string (UUIDv4 format without dashes).
string
required
The unique identifier (ID) or human-readable slug of the Sentry project.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_INGEST_EVENT_VIA_DSNIngests a single custom event into a Sentry project using its DSN via the Envelope ingestion endpoint. This may create or update an issue group depending on Sentry’s grouping algorithm. Note: Sentry does not provide a direct API to ‘create an issue group’; issues are created from ingested events. This tool allows controlled generation of events for testing or workflows requiring synthetic events.

Input Parameters

string
required
The Sentry DSN (Data Source Name) string in format: {PROTOCOL}://{PUBLIC_KEY}@{HOST}{PATH}/{PROJECT_ID}. This is used to authenticate and route the event to the correct project.
object
Key-value pairs for tagging the event. Each tag value must be a string and less than 200 characters.
object
Arbitrary additional metadata to attach to the event. All values will be converted to strings.
string ("fatal" | "error" | "warning" | "info" | "debug")
Event severity level. Defaults to ‘error’.
string
Logger name that created the event.
string
The error message. Either ‘message’ or ‘exception’ must be provided. Use message for simple log-like events.
string
Release version identifier for this event.
string
User ID for user context.
string
Optional event ID (32-character hex UUID without dashes). If not provided, one will be auto-generated.
string
Platform/SDK identifier. Defaults to ‘python’.
string
User email for user context.
string
Environment name where the event occurred.
array
List of strings used to control event grouping/deduplication. By default, Sentry groups events by stack trace.
string
Username for user context.
string
The exception type/class name. Required if you want to send an exception instead of a message.
string
The exception message/value. Used in conjunction with exception_type.
string
User IP address for user context.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_LIST_AN_ORGANIZATION_S_CLIENT_KEYSLists all client keys (DSNs) across all projects in an organization. Use when you need to audit keys organization-wide or filter keys by team or status.

Input Parameters

string
Filter keys by team slug or ID. If provided, only keys for projects belonging to this team will be returned.
string
A pointer to the last object fetched and its sort order; used to retrieve the next or previous results.
string ("active" | "inactive")
Status values for filtering client keys.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_LIST_AN_ORGANIZATIONS_ISSUESReturns a list of issues (error groups) for an organization. Use when you need to retrieve and analyze error patterns, track unresolved issues, or monitor issue trends. Default query applies ‘is:unresolved issue.priority:[high,medium]’.

Input Parameters

string
Query period end time in ISO-8601 format (e.g., 2001-12-14T12:34:56.7890).
string ("date" | "freq" | "inbox" | "new" | "trends" | "user")
Sort order for issues.
integer
Maximum number of issues to return. Default: 100, Maximum: 100.
string
Search query for filtering issues. Defaults to ‘is:unresolved issue.priority:[high,medium]’. Use an empty string to return all results. Must follow Sentry search syntax; malformed or overly narrow queries silently return empty results.
string
Query period start time in ISO-8601 format (e.g., 2001-12-14T12:34:56.7890).
string
Pagination cursor to retrieve next or previous results. Iterate using Link response headers until exhausted to retrieve all results.
array
Additional data to include in the response. Valid choices: inbox, integrationIssues, latestEventHasAttachments, owners, pluginActions, pluginIssues, sentryAppIssues, sessions.
string
View ID to apply custom query and filters.
array
Filter issues by project IDs. Use -1 to include all available projects.
array
Fields to exclude from the response. Valid choices: base, filtered, lifetime, stats, unhandled.
array
Filter issues by environment names. Pass multiple environment names to filter by multiple environments.
string
Time period for the query (e.g., 24h, 7d, 14d). Supports d (days), h (hours), m (minutes), s (seconds), w (weeks) suffixes. Overrides start and end parameters. Affects stats display only, not which issues are returned; use start/end or filter on dateCreated/lastSeen for precise time-bounded issue sets.
string ("0" | "1")
Parse query for short IDs when set to 1.
string ("14d" | "24h" | "auto")
Stats timeline period.
string
required
The ID or slug of the organization to retrieve issues from.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_LIST_A_PROJECTS_USER_FEEDBACKRetrieves a list of legacy user feedback items within a Sentry project. Use when you need to see user-reported feedback on errors. Note: This returns legacy User Reports, not submissions from the User Feedback Widget.

Input Parameters

string
Pagination cursor for retrieving the next or previous page of results.
integer
Maximum number of feedback items to return per page. Default: 100.
string
required
The ID or slug of the project.
string
required
The ID or slug of the organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_LIST_A_TAGS_VALUES_FOR_AN_ISSUERetrieves values and statistics for a specified tag key on a Sentry issue, optionally filtered by environment. Use it to analyze tag value frequency and when values were seen.

Input Parameters

string
required
The tag key to look the values up for (e.g., ‘level’, ‘environment’, ‘browser’).
integer
required
The ID of the issue to retrieve tag values for.
array
The name of environments to filter by.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_LIST_ORGANIZATION_DASHBOARDSRetrieves a list of custom dashboards for a Sentry organization, with pagination support.

Input Parameters

string
Opaque cursor for pagination, used to retrieve the next or previous page of dashboards. Obtain from the ‘Link’ header or pagination metadata of a previous API response.
integer
Maximum number of dashboard records per page. Defaults to Sentry’s setting (often 50) if unspecified. Max: 100.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization whose dashboards are to be listed.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_LIST_ORGANIZATION_MEMBERSLists all members, including those with pending invitations, for a Sentry organization.

Input Parameters

string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

string
An optional string to filter releases. The filter performs a “starts with” match on the release version. For example, “1.0” would match “1.0.1” and “1.0-beta”, while “backend-” would match “backend-v2.1”. If omitted, all releases are returned.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization whose releases are to be listed.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

string
required
The unique identifier (ID or slug) of the Sentry organization for which to list repositories. The slug is the URL-friendly name of the organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_LIST_ORGANIZATIONSRetrieves a list of organizations available to the authenticated session. Use this action when you need to discover which organizations the user has access to before performing operations on a specific organization. This is essential for organization-bound operations that require an organization_id_or_slug parameter. Note that API key requests only return the associated organization.

Input Parameters

boolean
Specify true to restrict results to organizations in which you are an owner. When false or omitted, returns all organizations you have access to.
string
Search query to filter organizations. Supports filtering by id, slug, status, email, member_id, and query fields.
string
Pagination cursor to retrieve the next or previous results. Use the cursor value from the Link header of a previous response.
string
Field to sort results by in descending order. Valid values: ‘members’ (sort by member count) or ‘events’ (sort by event count).

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_LIST_ORGANIZATION_USER_TEAMSRetrieves a list of all teams that the authenticated user has access to within the specified Sentry organization.

Input Parameters

string
required
The unique identifier (numeric ID like ‘4508539392294912’) or URL-friendly slug (like ‘my-organization’) of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_LIST_PROJECT_TAGSRetrieves all tags that have been recorded for events within a Sentry project, along with statistical information for each tag. Use when you need to understand what tags are available in a project and their usage patterns. This provides an overview of tag distribution and helps identify commonly used tags for filtering and analysis.

Input Parameters

string
required
The unique identifier (ID) or human-readable slug of the Sentry project.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_LIST_PROJECT_USERSRetrieves users who have interacted with or are recognized within a specific Sentry project, optionally filtered by a query.

Input Parameters

string
An optional query string to filter the list of users. Use prefixes like id:, email:, username:, or ip: to target specific fields. For example, email:foo@example.com or username:john.doe.
string
required
The unique identifier (ID) or human-readable slug for the Sentry project.
string
required
The unique identifier (ID) or human-readable slug for the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

integer
Maximum number of user records per response (max 100).
string
SCIM filter expression to narrow down users (e.g., userName eq "user@example.com"). Only eq operator is supported.
integer
The 1-based starting index for pagination.
array
Attribute names to exclude from user objects; only members is currently supported for exclusion.
string
required
The organization’s unique identifier (ID) or human-readable slug.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_LIST_SEER_AI_MODELSRetrieves the list of AI models currently used in production in Seer. Use when you need to discover which LLM models Seer is actively using.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_LIST_TEAMS_IN_ORGANIZATIONLists teams for an existing Sentry organization, optionally including project details and supporting pagination via a cursor.

Input Parameters

string
Pagination cursor for retrieving the next or previous page of results.
string
If ‘1’, includes project details for each team. If ‘0’ or not provided, excludes project details.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_MANAGE_TEAM_EXTERNAL_INTEGRATIONSLinks 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 ID.

Input Parameters

string ("github" | "github_enterprise" | "slack" | "gitlab" | "msteams" | "jira_server" | "perforce" | "custom_scm")
required
The third-party integration provider. Supported values: github, github_enterprise, jira_server, slack, perforce, gitlab, msteams, custom_scm.
string
Optional: The associated user ID for the provider (e.g., Slack user ID like U123ABC456).
string
required
The associated name for the provider (e.g., Slack channel name like #engineering, GitHub team like @dev-team).
integer
required
The Integration ID from Sentry. Use the ‘retrieve_organization_integrations_list’ action to find valid integration IDs for your organization.
string
required
The ID or slug of the team the resource belongs to.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_MODIFY_ORGANIZATION_NOTIFICATION_ACTIONModifies an organization’s notification action, specifically for spike-protection triggers.

Input Parameters

array
required
A list of project slugs for which this notification action will be active. For spike-protection triggers, this parameter is REQUIRED and must contain exactly one project slug. The notification action will apply only to the specified project.
integer
required
The unique numerical ID of the specific notification action to be modified. You can obtain this ID from the ‘view_organization_notification_actions’ action or from the response when creating a notification action.
string
required
The service through which the notification will be sent. For spike-protection triggers, use sentry_notification for built-in Sentry notifications. Other supported services include slack, pagerduty, and opsgenie (these require additional configuration via integration_id, target_identifier, and target_display parameters).
string
required
Specifies the type of event that triggers the notification. Currently, the only supported value is spike-protection.
integer
The ID of the integration for the notification service. Required if service_type is slack, pagerduty, or opsgenie. Not needed for sentry_notification service type.
string
A human-readable name for the notification target (e.g., a Slack channel name like ‘#critical-alerts’ or an Opsgenie team name). This is required if service_type is slack or opsgenie.
string
The unique identifier of the notification target within the chosen service (e.g., a Slack channel ID like ‘C012AB3CD’ or an Opsgenie team ID). This is required if service_type is slack or opsgenie.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization to which this notification action belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

string
A new name for the organization.
string
A new unique slug for the organization, used in URLs.
string
Base64 encoded image for the organization avatar; required if avatarType is ‘upload’.
string ("letter_avatar" | "upload")
Type of organization avatar: ‘letter_avatar’ (initials) or ‘upload’ (custom image).
boolean
Enforce two-factor authentication (2FA) for all members.
array
List of global field names exempt from data scrubbing, ensuring their values are preserved.
string ("member" | "admin" | "manager" | "owner")
Default role for new members when they join the organization.
boolean
Allow Sentry to comment on recent GitHub PRs suspected of introducing new issues. Requires GitHub integration.
boolean
Enforce server-side data scrubbing for all projects based on defined rules.
boolean
Enable Code Coverage Insights (Team plan or higher).
array
List of local Relay configurations. Each is a dict with name, publicKey, description. Business/Enterprise plans. Warning: Overwrites existing configurations.
boolean
Cancel a pending deletion and restore the organization.
string ("member" | "admin" | "manager" | "owner")
Minimum role to download debug files (e.g., ProGuard mappings, source maps).
boolean
Hide AI-powered features in the Sentry UI for this organization.
boolean
Opt the organization into new Sentry features before public release.
boolean
Allow members to freely join any team without invitation or approval.
string
JSON string defining advanced, project-specific data scrubbing rules. Applies to new events and overwrites existing advanced configuration. Warning: Updating this field overwrites all existing advanced rules.
string ("member" | "admin" | "manager" | "owner")
Minimum role to download event attachments (e.g., crash reports, logs).
boolean
Activate enhanced privacy controls, limiting PII and source code display (e.g., in notifications).
boolean
Allow Sentry to comment on open GitHub PRs with related error issues. Requires GitHub integration.
array
List of global field names whose values will be scrubbed from event data across all projects.
boolean
Allow Sentry to fetch missing JavaScript source context from public URLs if source maps are incomplete.
boolean
Prevent storage of IP addresses for new events in this organization.
boolean
Grant members alerts:write scope for alert rule management.
boolean
Allow users to request to join the organization; admins approve/deny.
boolean
Enable sharing limited issue details with anonymous users (e.g., via public links).
boolean
Grant members event:admin scope to delete events.
boolean
Enable Sentry to detect GitHub committers not in Sentry org and suggest inviting them. Requires GitHub integration.
integer
Number of native crash reports (e.g., Minidumps) to store per issue (0=Disabled, -1=Unlimited).
boolean
Apply Sentry’s default scrubbing rules (e.g., for passwords, credit cards) to event data for all projects.
boolean
Configure Sentry Slack integration to post Issue Alert replies in threads. Requires Slack integration.
boolean
Configure Sentry Slack integration to post Metric Alert replies in threads. Requires Slack integration.
string
required
The ID or slug of the organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_MODIFY_RELEASE_FILE_ATTRIBUTESUpdates attributes (e.g., name, distribution) of a specific file within an existing release, identified by organization, version, and file ID.

Input Parameters

string
The new distribution name for the file (e.g., build number, platform identifier). This is optional and can be used to differentiate files with the same name across different builds or platforms.
string
The new name (full path) for the file. While technically optional, the Sentry API requires this field to be provided when making updates (you can provide the current name if you don’t want to change it).
string
required
ID of the file to modify, typically a hash or unique identifier.
string
required
Version identifier of the release.
string
required
ID or slug of the organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_MUTATE_AN_ORGANIZATION_S_ALERTSBulk enable or disable alerts for an organization. Use when you need to activate or deactivate multiple alerts at once. This endpoint is in beta and may change in the future.

Input Parameters

array
The IDs of specific alerts to mutate. Provide one or more alert IDs to target specific alerts. If not provided, all matching alerts will be mutated.
string
An optional search query for filtering alerts to mutate. Use this to narrow down which alerts should be enabled or disabled.
boolean
required
Whether to enable or disable the alerts. Set to true to enable alerts, false to disable them.
array
The IDs of projects to filter by. Use -1 to include all available projects. For example: [1234, 5678] or [-1].
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_MUTATE_AN_ORGANIZATIONS_MONITORSBulk enable or disable monitors for an organization. This endpoint is in beta and may change. Use when you need to enable or disable multiple monitors at once based on filters.

Input Parameters

array
The ID of the monitor you’d like to query.
string
An optional search query for filtering monitors.
boolean
required
Whether to enable or disable the monitors.
array
The IDs of projects to filter by. -1 means all available projects. For example: /?project=1234&project=56789 or /?project=-1
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

integer
required
The unique identifier of the Sentry team to be updated.
array
required
A list of SCIM patch operations to be applied to the team. Each operation specifies an action (e.g., add, remove, replace), a target path, and a value. Multiple operations can be provided to perform several updates in a single request.
string
required
The ID or slug of the Sentry organization to which the team belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_PATCH_USER_ACTIVE_STATUS_IN_ORGANIZATIONDeactivates and permanently deletes a Sentry organization member by using a SCIM PATCH operation to set their ‘active’ attribute to ‘false’.

Input Parameters

string
required
The ID of the organization member to update.
array
required
A list of SCIM PATCH operations. For this action, must contain one operation setting the member’s ‘active’ attribute to ‘false’, which deactivates and permanently deletes the member.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_POST_SPIKE_PROTECTION_FOR_ORGANIZATIONEnables or updates Spike Protection for specified projects (or all projects using ['$all']) within an existing Sentry organization, to which the projects must belong.

Input Parameters

array
required
List of project slugs to enable Spike Protection for; use ['$all'] for all projects in the organization.
string
required
Unique ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_QUERY_EXPLORE_EVENTS_IN_TIMESERIES_FORMATRetrieves explore data for an organization as a timeseries for a selected dataset and aggregate axis, optionally grouped by top events.

Input Parameters

string
The end of the period of time for the query, expected in ISO-8601 format. For example, 2001-12-14T12:34:56.7890. This parameter is ignored if statsPeriod is provided.
string
What to order the results of the query by. Must be something in the field list, excluding equations.
string
Filters results by using query syntax. Example: (transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def).
string
The start of the period of time for the query, expected in ISO-8601 format. For example, 2001-12-14T12:34:56.7890. This parameter is ignored if statsPeriod is provided.
string
The aggregate field to create the timeseries for, defaults to count() when not included.
string ("logs" | "profile_functions" | "spans" | "uptime_results")
required
Which dataset to query. Changing datasets changes the available fields that can be queried. Options: ‘logs’, ‘profile_functions’, ‘spans’, ‘uptime_results’.
array
List of fields to group by. Required for topEvents queries as this and sort determine what the top events are.
array
The IDs of projects to filter by. -1 means all available projects. For example, the following are valid parameters: [1234, 56789] or [-1].
integer
The size of the bucket for the timeseries to have, must be a value smaller than the window being queried. If the interval is invalid a default interval will be selected instead.
integer
The number of top event results to return, must be between 1 and 10. When topEvents is passed, both sort and groupBy are required parameters.
array
The name of environments to filter by.
string
The period of time for the query, will override the start & end parameters. A number followed by one of: ‘d’ (days), ‘h’ (hours), ‘m’ (minutes), ‘s’ (seconds), ‘w’ (weeks). For example, 24h means query data starting from 24 hours ago to now.
string ("0" | "1")
Whether to include the ‘other’ timeseries in TopEvents queries.
integer
The delta in seconds to return additional offset timeseries by.
string
required
The ID or slug of the organization the resource belongs to.
string ("0" | "1")
Whether to throw an error when aggregates are passed.
string ("0" | "1")
Whether to disable aggregate extrapolation.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_A_CUSTOM_INTEGRATION_BY_ID_OR_SLUGRetrieves detailed information about a custom integration (Sentry App) by its slug. Use this action when you need to: - Get configuration details of a custom integration including scopes, webhooks, and OAuth settings - Check the status and permissions of an integration - Retrieve integration metadata such as name, description, and avatar - Verify which events an integration subscribes to Note: Provide the integration’s slug (case-sensitive), not its UUID.

Input Parameters

string
required
The URL-friendly slug of the custom integration (Sentry App) to retrieve. Note: Use the slug (e.g., ‘my-integration’), not the UUID. Slugs are case-sensitive.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_AGGREGATED_TEST_RESULT_METRICSRetrieves aggregated test result metrics for a repository, owner, and organization. Use when you need to analyze test performance and reliability metrics for a specific repository.

Input Parameters

string
required
The owner of the repository.
string
The branch to search for results by. If not specified, the default is all branches.
string
Time interval for results. Options: INTERVAL_30_DAY, INTERVAL_7_DAY, INTERVAL_1_DAY. If not specified, defaults to INTERVAL_30_DAY.
string
required
The name of the repository.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ALERT_RULE_DETAILSRetrieves detailed information for a specific metric alert rule within a Sentry organization. Note: This endpoint is specifically for metric alert rules (organization-level alerts based on metrics like error count, latency, failure rate, etc.). For issue alert rules (project-level alerts triggered by events), use the project rules endpoint instead. The API may return 404 if: - The alert rule ID does not exist - The organization does not have metric alerts enabled - The organization does not exist or you don’t have access

Input Parameters

integer
required
The numeric ID of the metric alert rule.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_A_MONITORRetrieves detailed information for a specific monitor within an organization. Use when you need to check monitor configuration, status, schedule, environments, or alert settings.

Input Parameters

array
Optional list of environment names to filter monitor details by. If omitted, all environments are included.
string
required
The ID or slug of the monitor to retrieve details for.
string
required
The ID or slug of the organization the monitor belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_COMMIT_FILES_FOR_RELEASERetrieves files changed in commits for a specified Sentry release; the release must exist and have linked commits.

Input Parameters

string
required
The version identifier of the release. This can be a semantic version string (e.g., ‘1.0.0’, ‘my-project@2.3.4-beta’), a descriptive name (e.g., ‘backend-deploy-2024-05-20’), or a commit SHA if used as the version string (e.g., ‘abcdef123456’).
string
required
The slug (e.g., my-org-slug) or numerical ID (e.g., 1234567) of the Sentry organization to which the release belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_COMMITS_FOR_ORGANIZATION_REPORetrieves a list of commits for a given repository within a Sentry organization.

Input Parameters

string
required
The unique identifier of the repository.
string
required
The unique identifier or short name (slug) of the organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_DATA_FORWARDERS_FOR_AN_ORGANIZATIONReturns a list of data forwarders for an organization. Use when you need to retrieve all data forwarders configured for a specific organization.

Input Parameters

string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_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.

Input Parameters

string
required
The unique identifier (ID) or human-readable slug of the Sentry project.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_EVENT_ID_FOR_ORGANIZATIONResolves a Sentry event ID to its project and issue details within an accessible Sentry organization.

Input Parameters

string
required
The unique 32-character hexadecimal identifier of the Sentry event to be resolved.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization where the event occurred. This specifies the scope for the event lookup.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_FILES_FOR_RELEASERetrieves a list of artifact files for a specific release version in a Sentry organization.

Input Parameters

string
required
The specific version identifier of the release. This can be a commit hash (e.g., ‘4018a1c’), a semantic version (e.g., ‘1.0.0’), a custom release name (e.g., ‘my-project@1.0.0’), or the literal string ‘latest’.
string
required
The unique identifier (ID) or human-readable name (slug) of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ISSUE_EVENTS_BY_IDRetrieves events for a specified Sentry issue_id, which must be an existing issue.

Input Parameters

string
The end timestamp for filtering events, in ISO-8601 format (e.g., 2001-12-14T12:34:56.7890Z). If provided, start must also be specified. This parameter is overridden by statsPeriod if both are used.
boolean
If set to true, the full event body, including stacktraces, is included in the response for each event. If false or not provided (default), summarized event data is returned.
string
An optional Sentry search query string to further filter events. Uses Sentry’s search syntax (e.g., ‘level:error’, ‘user.ip:127.0.0.1’, ‘handled:no tag_name:tag_value’).
string
The start timestamp for filtering events, in ISO-8601 format (e.g., 2001-12-14T12:34:56.7890Z). If provided, end must also be specified. This parameter is overridden by statsPeriod if both are used.
boolean
If set to true, events are returned in a pseudo-random yet deterministic order. An identical query will consistently produce the same event sequence. Useful for obtaining a representative sample from a large number of events.
integer
required
The unique numeric identifier of the Sentry issue for which to retrieve associated events.
array
A list of environment names (e.g., ‘production’, ‘staging’) to filter events by. Only events from these specified environments will be returned.
string
A relative time period for the query (e.g., ‘24h’, ‘7d’, ‘2w’), calculated from the current time. This overrides start and end if specified. Format is a number followed by ‘d’ (days), ‘h’ (hours), ‘m’ (minutes), ‘s’ (seconds), or ‘w’ (weeks).
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ISSUE_HASHES_FOR_ORGANIZATIONRetrieves a list of grouping checksums (hashes) generated by Sentry for a specific issue within an organization, used for understanding event aggregation.

Input Parameters

boolean
If True, includes comprehensive details for each hash; if False, returns a minimal representation.
string
Pagination cursor to navigate through the list of issue hashes.
string
required
Identifier (ID) of the Sentry issue.
string
required
Identifier (ID or slug) of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ISSUE_TAG_DETAILSRetrieves detailed information (e.g., top values, counts) for a specific tag key on an existing Sentry issue; results are paginated (max 1000 values per page).

Input Parameters

string
required
The specific tag key (e.g., ‘browser’, ‘os’, ‘environment’, ‘release’, custom tags) for which to retrieve detailed values; case-sensitive.
integer
required
The unique numerical ID of the Sentry issue.
array
Optional list of environment names to filter tag values; if omitted, all environments are considered.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_MONITOR_CHECKINSRetrieves the history of check-ins for a Sentry monitor, providing insights into the health and performance of associated scheduled tasks.

Input Parameters

string
required
The unique identifier (ID) or URL-friendly slug of the Sentry monitor. This specifies the monitor for which check-ins are to be retrieved.
string
required
The unique identifier (ID) or URL-friendly slug of the Sentry project. This specifies the project to which the monitor belongs, within the given organization.
string
required
The unique identifier (ID) or URL-friendly slug of the Sentry organization. This specifies the organization to which the project and monitor belong.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_MONITOR_CHECKINS_BY_ORGRetrieves check-ins (pings/heartbeats of a monitored cron job or task) for a specific monitor within a Sentry organization.

Input Parameters

string
required
The unique identifier (ID) or URL-friendly slug of the monitor.
string
required
The unique identifier (ID) or URL-friendly slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_NOTIFICATION_ACTION_BY_ORG_IDRetrieves details for a specific Spike Protection Notification Action, which defines alerts for triggered spike protection rules, within a Sentry organization.

Input Parameters

integer
required
The unique numerical identifier (ID) of the specific notification action to retrieve.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ORGANIZATION_DASHBOARDFetches detailed information about a specific custom dashboard within a Sentry organization.

Input Parameters

integer
required
The unique numeric identifier (ID) of the custom dashboard to retrieve within the specified organization.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ORGANIZATION_EVENTSRetrieves Discover event data for a Sentry organization. When a nonempty field list and sort are supplied, the tool adds the sort field to the list if missing; equation fields cannot be used for sorting, and the field list has a 20-item limit.

Input Parameters

string
The end timestamp for the query period, in ISO-8601 format (e.g., 2024-01-15T12:30:00Z). This parameter is ignored if statsPeriod is provided.
string
The field by which to sort the query results. Prepend with - for descending order (e.g., -timestamp). Important: The sort field must be included in the field parameter list and cannot be an equation field.
array
required
Specifies the fields, functions, or equations to include in the query results (maximum 20 items). Each item can be: - A built-in key field (e.g., id, title, timestamp, project, user.email, level, transaction, platform). - A tag, using tag[tagName] format (e.g., tag[browser.name]). - A function in function_name(parameters,...) format (e.g., count(), count_unique(user), avg(transaction.duration)). When a function is included, results are grouped by any non-aggregate fields. - An equation, prefixed with equation&#124; (e.g., equation&#124;count_if(transaction.duration,greater,300) / count() * 100). Note: The API automatically includes id and project.name fields in responses. If a sort parameter is provided, the base sort field will be automatically added to this list if not already present.
string
A Sentry search query string to filter events. Example: (transaction:foo AND release:abc) OR (transaction:[bar,baz] AND release:def). Refer to Sentry documentation for detailed search syntax.
string
The start timestamp for the query period, in ISO-8601 format (e.g., 2024-01-01T10:00:00Z). This parameter is ignored if statsPeriod is provided.
array
A list of project IDs (integers) to filter events by. Use [-1] to include all accessible projects. For example: [123, 456] or [-1].
integer
The maximum number of event rows to return per page. Defaults to 50 if not specified. Maximum allowed value is 100.
array
A list of environment names to filter events by (e.g., production, staging).
string
The relative time period for the query (e.g., 24h, 7d, 30m). This overrides start and end if provided. Valid suffixes: d (days), h (hours), m (minutes), s (seconds), w (weeks).
string
required
The ID or slug of the organization for which to retrieve events.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ORGANIZATION_INTEGRATIONS_LISTRetrieves a list of available integrations for an existing Sentry organization.

Input Parameters

array
Filters integrations by their supported features. Refer to Sentry’s Integrations Documentation for an updated list of features. Examples include: alert-rule, chat-unfurl, codeowners, commits, data-forwarding, deployment, enterprise-alert-rule, enterprise-incident-management, incident-management, issue-basic, issue-sync, mobile, serverless, session-replay, stacktrace-link, ticket-rules.
string
Filters integrations by a specific provider key. Refer to Sentry’s Integrations Documentation for an updated list of providers.
boolean
If True, fetches detailed third-party configurations for each integration; this may significantly increase response time.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ORGANIZATION_MEMBERRetrieves details for a Sentry organization member or pending invitee, including role, teams, and status, using their member ID and the organization’s ID or slug.

Input Parameters

string
required
The unique identifier (ID) of the organization member whose details are to be retrieved.
string
required
The unique identifier (ID) or URL-friendly slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ORGANIZATION_MONITORSRetrieves cron monitors for a Sentry organization, including details of nested monitor environments.

Input Parameters

string
Filter by owner, using user:<user_id> or team:<team_id> format.
array
List of project IDs to filter by; use [-1] for all accessible projects.
array
List of environment names (e.g., ‘production’, ‘staging’) to filter by.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ORGANIZATION_PROJECTSRetrieves a list of Sentry projects for a specified organization (which must be accessible), supporting pagination via cursor. Note: The {region} placeholder in the base URL is handled by the ApiAction framework, which overrides it with the base_url from auth metadata (typically ‘https://sentry.io’). This ensures correct URL construction regardless of the region placeholder in the template.

Input Parameters

string
Pagination cursor pointing to the next or previous set of results. If omitted, the first page is returned. Typically obtained from a previous response’s ‘Link’ header.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ORGANIZATION_RELAY_USAGERetrieves a list of trusted Sentry Relays configured for an organization. Sentry Relay is a service that proxies events between your application and Sentry. This endpoint returns the configuration of trusted relays registered for an organization. Each trusted relay entry includes details such as the relay name, public key for authentication, and a description of its purpose. Note: This feature is typically available for organizations on Business and Enterprise plans that have Relay infrastructure enabled. Organizations without any configured relays will return an empty list. Use this to: - View all trusted relays configured for your organization - Verify relay configurations and public keys - Audit relay infrastructure setup

Input Parameters

string
required
The unique identifier (ID) or human-readable slug for the Sentry organization. This specifies which organization’s relay usage data to retrieve.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ORGANIZATION_RELEASE_COMMITSRetrieves a list of commits for a given release version in an existing Sentry organization, if the release exists.

Input Parameters

string
required
The version identifier of the release. This can be a version number, package name with version, or a commit hash.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization to which the release belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ORGANIZATION_REPLAYSFetches session replays for a Sentry organization; use statsPeriod for relative time, or start and end (used together) for absolute time ranges.

Input Parameters

string
Absolute inclusive end of the time series range (UTC ISO8601 or epoch seconds). Requires start. Conflicts with statsPeriod.
string
The field to sort the replays by. Prefix with ’-’ for descending order (e.g., ‘-started_at’). Default is ‘activity’.
array
Additional fields to include in the response for each replay; invalid fields are ignored.
string
Structured query string to filter replays (e.g., ‘user.email:“j.doe@example.com” AND browser.name:“Chrome”’). Refer to Sentry documentation for syntax.
string
Absolute start of the time series range (UTC ISO8601 or epoch seconds). Requires end. Conflicts with statsPeriod.
string
Pagination cursor for fetching next/previous page. See Sentry API documentation for details.
array
A list of project IDs to filter replays by. Use -1 for all projects.
integer
The maximum number of replays to return per page. The default is 50, and the maximum is 100.
string
The environment name to filter replays by (e.g., ‘production’, ‘staging’).
string
The relative time range for the query (e.g., 1d for one day). Units: m (minutes), h (hours), d (days), w (weeks).
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ORGANIZATION_SCIM_GROUPSRetrieves a paginated list of SCIM groups (teams) for a Sentry organization; the members field in the response for each group will contain at most 10,000 members.

Input Parameters

integer
The maximum number of SCIM groups to return per page. The API enforces a maximum limit of 100.
string
A SCIM filter expression to narrow down the list of groups. Currently, only the eq (equals) operator is supported, e.g., displayName eq "Engineering Team".
integer
The 1-based index for pagination, indicating the starting point of the results to retrieve. Follows SCIM standards.
array
A list of attribute names to exclude from the response for each group. Currently, the only supported value for an attribute to exclude is members.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization for which to retrieve SCIM groups.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ORGANIZATION_STATS_V2Retrieves Sentry organization event statistics; specify time range with statsPeriod OR both start/end; note that grouping by project returns a sum not a time-series, and interval (if used) must be 1h-1d and cleanly divide 24 hours.

Input Parameters

string
Inclusive end timestamp for the time series (ISO 8601 UTC or Unix epoch seconds). Use with start; alternative to statsPeriod.
string ("sum(quantity)" | "sum(times_seen)")
required
Metric to retrieve. sum(quantity) for event counts (or bytes if category is attachment, milliseconds if profile_duration). sum(times_seen) for unique event occurrences (or sessions/attachments).
string
Start timestamp for the time series (ISO 8601 UTC or Unix epoch seconds). Use with end; alternative to statsPeriod.
string
Reason an event was filtered/dropped by Sentry (e.g., filters:release_version, spike_protection). Often used with outcomes like filtered or rate_limited.
array
required
Dimensions to group statistics by. IMPORTANT: The query must include category either in groupBy OR as a filter parameter. Grouping by project returns a sum over the entire period, not a time series; for many projects, consider filtering by projects individually or querying them one by one to avoid missing rows.
string ("accepted" | "filtered" | "rate_limited" | "invalid" | "abuse" | "client_discard" | "cardinality_limited")
Filter by event outcome status (e.g., accepted, filtered, rate_limited), indicating how Sentry processed the event.
array
Project IDs to filter statistics by. Use ["-1"] to include all accessible projects for the organization.
string ("error" | "transaction" | "attachment" | "replay" | "profile" | "profile_duration" | "monitor")
Filter by data category (e.g., error, transaction). IMPORTANT: Either this parameter OR category in groupBy is required for the query to succeed. attachment and profile_duration categories affect interpretation of sum(quantity) in field (bytes and milliseconds respectively).
string
Time series data resolution (e.g., 1h, 1d). Must be between 1h and 1d (inclusive) and cleanly divide 24 hours (e.g., 1h, 2h, 6h, 12h, 24h).
string
Relative time range for statistics (e.g., 1d for 1 day, 2w for 2 weeks). Use m (minutes), h (hours), d (days), w (weeks). Provide this or both start and end.
string
required
ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_ORG_INTEGRATION_CONFIGRetrieves configuration for all integrations, or a specific integration if providerKey is given, for an existing Sentry organization.

Input Parameters

string
Key of a specific integration provider (e.g., ‘slack’, ‘github’, ‘jira’) to filter by; if omitted, returns configurations for all integrations. Refer to Sentry’s documentation for supported provider keys.
string
required
The ID or slug of the Sentry organization for which to retrieve integration configurations.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PAGINATED_REPOSITORY_TOKENSRetrieves a paginated list of repository tokens for a given owner. Use when you need to access repository tokens with pagination support.

Input Parameters

integer
The number of results to return per page. Defaults to 20 if not specified.
string
required
The owner of the repository (e.g., GitHub organization or user).
string
Cursor marking the position in the result set for pagination navigation. Obtain this from pageInfo in the previous response.
string
Field to sort results by. Supports ‘NAME’ (alphabetical) or ‘COMMIT_DATE’ (most recent first, default). Defaults to ‘COMMIT_DATE’ in descending order.
string
Controls pagination direction. Use ‘next’ to fetch the next page or ‘prev’ to fetch the previous page. Defaults to ‘next’.
string
required
The ID or slug of the organization that the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PROJECT_ENVIRONMENTSRetrieves a list of environments for an existing project within a Sentry organization.

Input Parameters

string ("all" | "hidden" | "visible")
Filters environments by their visibility status: all, hidden, or visible.
string
required
The ID or slug of the project for which environments are to be retrieved.
string
required
The ID or slug of the organization to which the project belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PROJECT_EVENT_BY_IDRetrieves detailed information for a specific Sentry event using its ID, organization identifier, and project identifier.

Input Parameters

string
required
The hexadecimal ID of the event to retrieve, as reported by the client.
string
required
The unique identifier (ID or slug) of the Sentry project to which the event belongs.
string
required
The unique identifier (ID or slug) of the Sentry organization to which the event belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PROJECT_FILTER_DATARetrieves a Sentry project’s current data filtering settings, used to ignore events from sources like localhost, web crawlers, or legacy browsers.

Input Parameters

string
required
Unique identifier (ID) or human-readable slug of the Sentry project.
string
required
Unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PROJECT_HOOKSReturn a list of service hooks (webhooks) bound to a Sentry project, used to send notifications to external services upon event occurrences.

Input Parameters

string
Pagination cursor to retrieve the next or previous set of results (e.g., ‘100:0:1’).
string
required
The ID or slug of the Sentry project.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PROJECT_ISSUES_LISTRetrieves a list of issues for a Sentry project, defaulting to unresolved issues unless an empty query string is provided or specific hashes are used.

Input Parameters

string
Sentry structured search query to filter issues (e.g., “is:resolved”, “error.type:TypeError”). Defaults to “is:unresolved”; "" retrieves all issues regardless of status. IMPORTANT: Boolean operators “OR” and “AND” are NOT supported in Issue search - they will cause an error. To search multiple values for the same key, use list syntax: key:[value1, value2] instead of key:value1 OR key:value2. Use negation with ! prefix (e.g., !is:resolved) to exclude results.
string
Pagination cursor from a previous response’s Link header to fetch the next/previous set of issues.
string
Comma-separated group hashes to retrieve specific issues; incompatible with query. Max 100 hashes processed.
string
Time window for calculating issue statistics (affects the timeline stats in the response, not which issues are returned). Valid values: "" (empty string to disable stats), “24h” (last 24 hours), “14d” (last 14 days). Defaults to “24h” if not provided. Other values (e.g., “7d”, “1h”, “30d”) are not supported.
boolean
If True, enables issue lookup by short IDs; may return issues from a different project. API default is typically False.
string
required
Unique identifier (ID) or human-readable slug of the Sentry project.
string
required
Unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PROJECT_KEY_DETAILSRetrieves details of a specific client key (DSN) for a Sentry project, which is used by Sentry SDKs to send event data.

Input Parameters

string
required
ID of the client key (DSN).
string
required
ID or slug of the project.
string
required
ID or slug of the organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PROJECT_KEYS_BY_ORG_AND_PROJECTRetrieves a list of client keys (DSNs), used by Sentry SDKs to send events, for a specified project within an organization.

Input Parameters

string
Pagination cursor to retrieve the next or previous set of results, typically formatted as ‘<cursor_identifier>:<row_offset>:<is_prev>’.
string
Filter client keys by status: ‘active’ or ‘inactive’. If unspecified, returns all keys.
string
required
The ID or slug of the project.
string
required
The ID or slug of the organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PROJECT_MEMBERS_LISTRetrieves active organization members belonging to any team assigned to the specified Sentry project.

Input Parameters

string
required
The ID or human-readable slug of the Sentry project. This identifies the project for which members will be listed.
string
required
The ID or human-readable slug of the Sentry organization. This identifies the organization to which the project belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PROJECT_RELEASE_FILE_DETAILSRetrieves metadata (default) or raw content (if download is true) for a specific file within a Sentry project’s release version.

Input Parameters

string
required
The unique identifier of the file associated with the release (e.g., ’~/app.js.map’, ‘dist/bundle.js’).
string
required
The version identifier of the release (e.g., ‘1.0.0’, ‘my-app@2.3.1-beta’).
boolean
If true, returns raw file content; otherwise, returns file metadata (JSON object).
string
required
The unique identifier (ID) or human-readable slug of the Sentry project.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PROJECT_RULES_BY_ORG_AND_PROJECT_IDRetrieves a list of active issue alert rules associated with a specific project within an organization. Returns all active issue alert rules configured for the specified project, including their conditions, filters, actions, and metadata. This endpoint is useful for auditing alert configurations, managing alert rules programmatically, or understanding what alerts are active in a project.

Input Parameters

string
required
The unique identifier (ID) or human-readable slug of the project for which to retrieve alert rules.
string
required
The unique identifier (ID) or human-readable slug of the organization to which the project belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PROJECT_SYMBOL_SOURCESRetrieves custom symbol sources for a Sentry project, either listing all or fetching a specific one if its ID is provided.

Input Parameters

string
ID of a specific symbol source to retrieve; if omitted, all custom symbol sources for the project are returned.
string
required
The unique identifier (ID) or URL-friendly slug of the Sentry project.
string
required
The unique identifier (ID) or URL-friendly slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PROJECT_TAG_VALUESRetrieves values for a specified tag key recorded in a Sentry project. An empty list can also result from a 404 response or a non-list response.

Input Parameters

string
required
The specific tag key for which to retrieve the associated distinct values (e.g., ‘browser’, ‘device’, ‘environment’).
string
required
The unique identifier (ID) or human-readable slug of the Sentry project.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_PROJECT_TEAMSRetrieves a list of teams with explicit access to a specific project within a Sentry organization.

Input Parameters

string
required
ID or slug of the Sentry project.
string
required
ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_RELEASE_COMMITSRetrieves a list of commits associated with a specific release version within a Sentry project.

Input Parameters

string
required
The version identifier of the release. This can be a commit SHA, a semantic version string, or any unique string identifying the release (e.g., ‘my-app@1.0.0’, ‘cf7f4a337311e395e5099035f904289140b37025’).
string
required
The unique identifier (ID) or human-readable slug of the Sentry project to which the release belongs.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization to which the release belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_RELEASE_DEPLOYMENTSRetrieves a list of all deployment records for a specific release version in an organization, detailing each deployment’s environment and timestamps.

Input Parameters

string
required
The version identifier of the release. This can be a semantic version string (e.g., ‘1.0.0’), a project-qualified version (e.g., ‘my-project-name@1.0.0’), or a full commit SHA.
string
required
The unique identifier (ID or slug) of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_RELEASE_FILE_BY_IDRetrieves a specific file’s content or its metadata from a Sentry release, using the download parameter to choose between raw content or JSON metadata.

Input Parameters

string
required
The unique numeric identifier of the file within the specified release. This ID is returned in the ‘id’ field when listing release files via the ‘List an Organization’s Release Files’ endpoint.
string
required
The version identifier of the release, such as ‘1.0.0’, ‘backend@2.3.1-beta’, or a commit SHA.
boolean
Set to true to receive raw file content. If false or omitted, results in a JSON object with file metadata being returned.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_REPLAY_RECORDING_SEGMENTSRetrieves a paginated list of recording segments for a specific Sentry replay, for reconstructing or analyzing the replay. The replay is identified within its organization and project.

Input Parameters

string
Pagination cursor obtained from previous response to retrieve the next or previous set of results.
integer
Number of recording segments per page (default/max is 100).
string
required
The unique identifier (UUID format without hyphens) of the replay session to retrieve recording segments for.
string
required
ID or slug of the Sentry project.
string
required
ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_SAVED_DISCOVER_QUERIESRetrieves a paginated list of saved Discover query definitions for a Sentry organization, with name filtering and sorting. HTTP 404 responses are returned as an empty list without an explanatory message, so an empty result may also indicate an unavailable endpoint.

Input Parameters

string
A string to filter saved Discover queries by their name. For example, “High CPU Usage”.
string
An opaque pagination cursor that points to the last object fetched and its sort order. Used to retrieve the next or previous set of results.
string
Field to sort results by. Defaults to sorting by query name. Valid options: name (alphabetical), dateCreated (creation date), dateUpdated (last modified date), mostPopular (by usage frequency), recentlyViewed (by last view date), myqueries (queries created by the authenticated user).
integer
Maximum number of saved queries to return per page. Max: 100.
string
required
The ID or slug of the Sentry organization for which to retrieve saved Discover queries.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_SAVED_DISCOVER_QUERY_FOR_ORGANIZATIONRetrieves a specific saved Discover query (a predefined set of filters and conditions for exploring event data) for a Sentry organization.

Input Parameters

integer
required
The ID of the saved Discover query to retrieve.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_SEER_ISSUE_FIX_STATERetrieves the current detailed state of an AI-assisted autofix process for a Sentry issue. Use when you need to check the progress, status, root cause analysis, proposed solutions, or code modifications for an autofix operation.

Input Parameters

string
required
The ID of the issue to retrieve autofix state for.
string
required
The ID or slug of the organization the issue belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_SHORT_ID_FOR_ORGANIZATIONResolves a Sentry short ID (e.g., ‘PROJECT-1A’) to its complete issue details including organization slug, project slug, group ID, and full issue metadata. Use this to look up issue information when you have a short ID reference.

Input Parameters

string
required
The Sentry short ID to resolve (e.g., ‘PROJECT-1A’, ‘APP-XYZ’).
string
required
ID or slug of the Sentry organization where the short ID will be looked up.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_SOURCE_MAP_DEBUG_EVENTRetrieves source map debug errors for a Sentry event, stack trace frame, and exception index. Responses for HTTP 400, 404, and 500 return an error detail and status rather than raising an error.

Input Parameters

string
required
The unique identifier (ID) of the event for which source map debug information is being retrieved.
integer
required
Zero-based index of the specific stack trace frame to debug for source map resolution. Use 0 for the most recent frame. The API will return an error if the index is out of bounds.
integer
required
Zero-based index of the exception in the event’s exception array to debug for source map resolution. Use 0 for the primary exception. The API will return an error if the index is out of bounds or if the event does not contain exceptions.
string
required
The unique identifier (ID) or human-readable slug of the Sentry project to which the resource belongs.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization to which the resource belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_TEAM_INFO_VIA_ORGANIZATION_ID_OR_SLUGRetrieves detailed information for an existing Sentry team within its organization, optionally expanding related data (e.g., projects) or collapsing sections (e.g., organization details).

Input Parameters

string
A comma-separated string listing extra data sections to include in the response. Supported values are projects (to include details of projects associated with the team) and externalTeams (to include mappings to external teams). For example, ‘projects,externalTeams’.
string
A comma-separated string listing data sections to exclude from the response. Supported value is organization (to exclude detailed organization information from the team details).
string
required
The numeric ID or human-readable slug of the Sentry team whose details are to be retrieved. Use team slugs (e.g., ‘my-team’, ‘engineering’) or numeric IDs (e.g., ‘4506274564079616’). Note: UUID format identifiers are NOT supported by the Sentry API and will result in a 404 error.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization to which the team belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_TEAM_PROJECTSRetrieves a list of Sentry projects for a specific team within an organization, supporting pagination via a cursor.

Input Parameters

string
Pagination cursor for navigating through project lists; if omitted, the first page is returned.
string
required
The ID or slug of the Sentry team.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_THE_CUSTOM_INTEGS_CREATED_BY_AN_ORGRetrieves custom integrations (Sentry Apps) created by an organization. Use when you need to list all custom integrations that the organization has developed.

Input Parameters

string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_USER_EMAIL_INFORMATIONRetrieves a list of email addresses for an existing Sentry user, identified by their user_id.

Input Parameters

string
required
The unique identifier of the Sentry user for whom to retrieve email information.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_RETRIEVE_USER_VIA_SCIM_APIRetrieves an individual Sentry organization member’s details using the SCIM v2 API. Returns a SCIM-formatted user resource containing the member’s ID, username (email), email addresses, name (givenName and familyName), active status, and Sentry organization role. Requirements: This endpoint requires SCIM to be enabled for the organization, which requires a Business Plan subscription and SAML2 authentication enabled. A SCIM bearer token (not a regular API token) must be used for authentication. Note: Sentry’s SCIM API does not support syncing passwords or setting user attributes other than ‘active’.

Input Parameters

string
required
The SCIM member ID (organization member ID) of the user to retrieve. This is the same as the member ID returned by the List Organization Members endpoint.
string
required
The organization’s unique identifier (ID) or human-readable slug (e.g., ‘acme-corp’ or ‘1234567’)

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_SAVE_ORGANIZATION_DISCOVER_QUERYSaves a new Discover query with a unique name for a Sentry organization, allowing reuse of search criteria for analyzing event data (errors, transactions) across specified projects and environments.

Input Parameters

string
End date/time for the query’s time range (ISO 8601). Takes precedence over range.
string
required
Unique name for the saved query.
string
Search query string using Sentry’s syntax (e.g., level:error transaction:/api/v1/*).
string
Relative time range (e.g., ‘24h’, ‘7d’) if start and end are not provided.
string
Start date/time for the query’s time range (ISO 8601). Takes precedence over range.
array
List of aggregate functions for the y-axis of the chart visualization.
array
List of fields (e.g., transaction, tag[tagName]), functions (e.g., count_if(...)), or equations (prefixed with equation&#124;) to include (max 20). See Sentry documentation for details.
string
Chart visualization type. Allowed: default, previous, top5, daily, dailytop5, bar.
string
Field or function from fields list to order results by (prefix with - for descending). Cannot be an equation.
string
Time series resolution for the chart (e.g., ‘1h’, ‘30m’, ‘auto’).
array
List of project IDs to filter by; empty list implies all projects in the organization.
integer
Number of ‘top events’ timeseries for top5 or dailytop5 display types.
array
List of environment names to filter by.
string ("discover" | "error-events" | "transaction-like")
Dataset to query: discover (event properties/tags), error-events (error data), or transaction-like (transaction/performance data).
string
required
ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_START_SEER_ISSUE_FIXTrigger a Seer Issue Fix run for a specific issue. Use when you want to start an AI-assisted autofix process that operates asynchronously to identify root causes, propose solutions, generate code changes, and optionally create pull requests with fixes.

Input Parameters

string
Run issue fix on a specific event. If not provided, the recommended event for the issue will be used.
integer
required
The ID of the issue to trigger autofix for.
string
Optional custom instruction to guide the issue fix process. Provide specific guidance on how the fix should be approached.
string
Where the autofix process should stop: ‘root_cause’, ‘solution’, ‘code_changes’, or ‘open_pr’. Defaults to root cause if not specified.
string
URL of a pull request where the issue fix should add comments. Must be a valid GitHub pull request URL.
string
required
The ID or slug of the organization the issue belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_SUBMIT_NOTIFICATION_ACTION_API_DATACreates a Sentry notification action for ‘spike-protection’ triggers, requiring integration_id if service_type is ‘slack’, ‘pagerduty’, or ‘opsgenie’, and target_identifier/target_display if service_type is ‘slack’ or ‘opsgenie’.

Input Parameters

array
Optional list of project slugs to scope this action; if provided, the action applies only to these projects.
string
required
The service for sending the notification (e.g., ‘email’, ‘slack’).
string
required
Specifies the type of event that triggers the notification; currently, only ‘spike-protection’ is supported.
integer
ID of the pre-configured integration. Required if service_type is ‘slack’, ‘pagerduty’, or ‘opsgenie’.
string
Human-readable name for the notification target (e.g., Slack channel name). Required if service_type is ‘slack’ or ‘opsgenie’.
string
Specific identifier of the notification target (e.g., Slack channel ID). Required if service_type is ‘slack’ or ‘opsgenie’.
string
required
The unique identifier (ID or slug) of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_SUBMIT_USER_FEEDBACKSubmits user feedback tied to a specific Sentry event. Use when you need to associate user-reported issues with specific error events. DEPRECATED: This endpoint is maintained for legacy SDKs; new implementations should use the User Feedback Widget. Feedback must be submitted within 30 minutes of event creation and can only be modified within 5 minutes of submission.

Input Parameters

string
required
The name of the person submitting the feedback.
string
required
The email address of the person submitting the feedback.
string
required
The user’s feedback content describing the issue or experience.
string
required
The event identifier, retrievable via beforeSend callback. Must be from an event created within the last 30 minutes.
string
required
The ID or slug of the project.
string
required
The ID or slug of the organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_SWITCH_TEAM_ROLE_FOR_MEMBERChanges a member’s role within a Sentry team, ensuring the member is already part of the team and that any organization-level role restrictions are respected.

Input Parameters

string ("contributor" | "admin")
Details for available team roles: contributor allows viewing/acting on events and most team project data; admin grants team administration privileges like managing projects and memberships.
string
required
Identifier for the organization member.
string
required
Identifier (ID or slug) for the Sentry team.
string
required
Identifier (ID or slug) for the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_TOGGLE_PROJECT_FILTER_STATUSUpdates the status or configuration of a specific inbound data filter for a Sentry project; use active for most filters, or subfilters if filter_id is legacy-browsers.

Input Parameters

boolean
Enable (true) or disable (false) the filter. Required if filter_id is not legacy-browsers; not used if filter_id is legacy-browsers (use subfilters then).
string
required
Identifier of the inbound data filter to update. Each filter_id has a specific behavior: - browser-extensions: Filters errors known to be caused by browser extensions. - localhost: Filters events originating from localhost (IPv4: 127.0.0.1, IPv6: ::1). - filtered-transaction: Filters transactions for health check and ping endpoints. - web-crawlers: Filters known web crawlers, as they may cause errors unlikely for normal users. - legacy-browsers: Filters known errors from legacy browsers (often providing less accurate context). Use subfilters to configure specific browsers for this filter.
array
List of legacy browser subfilters to enable (unlisted ones will be disabled). Required and only used if filter_id is legacy-browsers. Available options: - ie: Internet Explorer (v11 and older) - edge: Edge (v18 and older, non-Chromium) - safari: Safari (v11 and older) - firefox: Firefox (v66 and older) - chrome: Chrome (v62 and older) - opera: Opera (v50 and older) - android: Android Browser (v3 and older) - opera_mini: Opera Mini (v34 and older) Deprecated options (still functional but may be removed in the future): - ie_pre_9: Internet Explorer (v8 and older) - ie9: Internet Explorer v9 - ie10: Internet Explorer v10 - ie11: Internet Explorer v11 - safari_pre_6: Safari (v5 and older) - opera_pre_15: Opera (v14 and older) - opera_mini_pre_8: Opera Mini (v8 and older) - android_pre_4: Android Browser (v3 and older) - edge_pre_79: Edge (v18 and older, non-Chromium based)
string
required
ID or slug of the Sentry project.
string
required
ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_A_MONITORUpdates a monitor’s configuration and settings. Use when you need to modify monitor name, schedule, check-in margin, max runtime, timezone, or alert thresholds.

Input Parameters

string
required
The name of the monitor. Used in notifications and the Sentry UI. This is required for updating a monitor.
string
A unique identifier for the monitor within the organization. Changing this slug requires updating any instrumented check-in calls. Must match pattern ^[a-z][a-z0-9_-]*$.
string
The ID of the team or user that owns the monitor. Format: ‘user:{user_id}’ or ‘team:{team_id}’.
object
required
The configuration object for the monitor, including schedule, checkin margin, max runtime, timezone, and alert thresholds.
string ("active" | "disabled")
The status of the monitor. ‘active’ monitors accept events and count towards quota; ‘disabled’ monitors do not.
string
required
The project slug to associate the monitor with. This is required for updating a monitor.
boolean
Whether to disable creation of monitor incidents. Set to true to suppress alerts for this monitor.
string
required
The ID or slug of the monitor to update.
string
required
The ID or slug of the organization the monitor belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_A_MONITOR_BY_IDUpdates an existing Sentry monitor (detector) for metric-based issue detection. Use when you need to modify monitor configuration, thresholds, data sources, or enable/disable the monitor. Note: This endpoint is in beta and may change.

Input Parameters

string
required
Name of the monitor.
string
required
The type of monitor. Must be ‘metric_issue’.
string
The user or team who owns the monitor. Can be a string or an object with type, id, name, and optional email.
object
Issue detection type configuration.
boolean
Set to false if you want to disable the monitor. Defaults to true.
integer
required
The ID of the monitor you’d like to update.
array
The data sources for the monitor to use based on what you want to measure (errors, transactions, spans, etc.).
string
A description of the monitor. Will be used in the resulting issue.
object
Issue detection configuration for when to create an issue and at what priority level.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_AN_ALERT_BY_IDUpdates a Sentry alert workflow by ID, including its name, filters, triggers, or configuration; the enabled setting defaults to true unless set otherwise or explicitly set to null. This endpoint is in beta and supported by New Monitors and Alerts.

Input Parameters

string
The ID of the existing alert
string
required
The name of the alert
object
Typically the frequency at which the alert will fire, in minutes. Valid values: 0 (0 minutes), 5 (5 minutes), 10 (10 minutes), 30 (30 minutes), 60 (1 hour), 180 (3 hours), 720 (12 hours), 1440 (24 hours)
boolean
Whether the alert is enabled or disabled
object
The conditions on which the alert will trigger. logicType can be one of: any-short, all, or none. Common trigger types include: first_seen_event, issue_resolved_trigger, reappeared_event, regression_event
string
The name of the environment for the alert to evaluate in
integer
required
The ID of the alert you’d like to query.
array
The filters to run before the action will fire and the action(s) to fire. logicType can be one of: any-short, all, or none. See API documentation for full schema of conditions and actions.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_AN_EXISTING_CUSTOM_INTEGRATIONUpdates an existing custom integration (Sentry App) with new configuration. Use this action to modify integration settings such as name, scopes, webhook URL, or other configuration. You must provide the integration’s slug or ID and the required fields (name and scopes).

Input Parameters

string
required
The name of the custom integration. This is the display name shown to users.
string
The custom integration’s author name or organization.
array
Webhook events the custom integration is subscribed to (e.g., ‘issue’, ‘comment’, ‘event.alert’).
object
The UI components schema, used to render the custom integration’s configuration UI elements. See Sentry’s schema docs for more information.
array
required
The custom integration’s permission scopes for API access (e.g., ‘project:read’, ‘event:read’, ‘org:read’). This field is required for updating the integration.
string
The custom integration’s description or overview text.
boolean
Whether or not the integration is internal only. False means the integration is public. Defaults to false if not specified.
string
The webhook destination URL where Sentry will send event notifications.
boolean
Marks whether or not the custom integration can be used in an alert rule. Defaults to false if not specified.
string
The post-installation redirect URL where users are sent after installing the integration.
boolean
Whether or not an installation of the custom integration should be verified. Defaults to true if not specified.
array
The list of allowed origins for CORS configuration.
string
required
The ID or slug of the custom integration to update. Use the slug (e.g., ‘my-integration’), not the UUID. Slugs are case-sensitive.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_A_PROJECTS_SYMBOL_SOURCEUpdates an existing custom symbol source (HTTP, GCS, or S3) in a project for fetching debug symbols. Use when you need to modify the configuration of a symbol source identified by its ID.

Input Parameters

string
required
The ID of the symbol source to update. This is passed as a query parameter.
string
Base URL for an HTTP symbol source. Required if type is ‘http’.
string
required
Human-readable name for the symbol source.
string ("http" | "gcs" | "s3")
required
Type of the symbol source. Required field that determines which additional fields are needed.
string
Name of the GCS or S3 bucket containing symbols. Required if type is ‘gcs’ or ‘s3’.
string
Optional path prefix within the GCS or S3 bucket.
string ("us-east-2" | "us-east-1" | "us-west-1" | "us-west-2" | "ap-east-1" | "ap-south-1" | "ap-northeast-2" | "ap-southeast-1" | "ap-southeast-2" | "ap-northeast-1" | "ca-central-1" | "cn-north-1" | "cn-northwest-1" | "eu-central-1" | "eu-west-1" | "eu-west-2" | "eu-west-3" | "eu-north-1" | "sa-east-1" | "us-gov-east-1" | "us-gov-west-1")
AWS region for the S3 bucket. Required if type is ‘s3’.
string
Password for HTTP basic authentication. Optional for HTTP sources.
string
Username for HTTP basic authentication. Optional for HTTP sources.
string
Optional internal ID of the source. Must be distinct from all other source IDs and cannot start with ‘sentry:’.
string
AWS Access Key ID for S3 authentication. Required if type is ‘s3’.
string
AWS Secret Access Key for S3 authentication. Required if type is ‘s3’.
string
Private key (PEM format) for GCS service account. Required if type is ‘gcs’.
string
Client email for GCS service account. Required if type is ‘gcs’.
string ("native" | "symstore" | "symstore_index2" | "ssqp" | "unified" | "debuginfod" | "slashsymbols")
Specifies the directory structure or layout type for symbols. Required for HTTP, GCS, and S3 sources.
string ("lowercase" | "uppercase" | "default")
Specifies the filename casing convention for symbols.
array
List of file types to filter. Optional filtering configuration.
string
required
The ID or slug of the project containing the symbol source.
array
List of glob patterns for path matching. Optional filtering configuration.
string
required
The ID or slug of the organization that owns the project.
boolean
Whether debug checksums are mandatory. Defaults to false if not specified.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_ENVIRONMENT_VISIBILITYUpdates the visibility of a specific environment within a Sentry project.

Input Parameters

boolean
required
Indicates if the environment should be hidden (true) or visible (false).
string
required
The name of the environment to update.
string
required
The ID or slug of the Sentry project.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_EXTERNAL_TEAM_INTEGRATIONUpdates an existing external team integration’s display name, provider, Sentry integration ID, or external ID; the integration_id must match a valid, configured Sentry integration for the organization and the specified provider.

Input Parameters

string ("github" | "github_enterprise" | "slack" | "gitlab" | "msteams" | "custom_scm" | "jira_server" | "perforce")
required
Provider of the external actor; must match the provider of the integration.
string
Optional: External ID for the team within the provider’s system, distinct from its name.
string
required
New display name for the team in the external provider.
integer
required
Unique ID of the Sentry integration instance connecting Sentry to the external provider.
string
required
ID or slug of the Sentry team.
integer
required
Unique ID of the external team object to update.
string
required
ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_EXTERNAL_USER_FOR_ORGANIZATIONUpdates attributes of an existing external user linkage (identified by external_user_id) within a Sentry organization (specified by organization_id_or_slug).

Input Parameters

integer
required
The unique Sentry identifier of the external user record being updated. This typically matches the external_user_id path parameter.
integer
required
The Sentry user ID to be linked or that is currently linked with this external user.
string ("github" | "github_enterprise" | "jira_server" | "slack" | "perforce" | "gitlab" | "msteams" | "custom_scm")
required
The external identity provider platform. Supported values: github, github_enterprise, jira_server, slack, perforce, gitlab, msteams, custom_scm.
string
The user’s unique identifier on the external provider’s platform (e.g., ‘U123ABC’ for Slack, ‘github_user_123’ for GitHub). This is optional.
string
required
The user’s display name or username on the external provider platform (e.g., ‘john.doe’ or ‘John Doe’).
integer
required
The Sentry ID of the integration instance (e.g., a specific Slack workspace or GitHub organization integration) through which this external user is known.
integer
required
The unique identifier of the external user record within Sentry to update.
string
required
The unique identifier (numeric ID or string slug) of the Sentry organization to which the external user is linked.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_ISSUE_ATTRIBUTES_IN_ORGANIZATIONUpdates specified attributes of an existing Sentry issue within a Sentry organization, leaving other attributes unchanged.

Input Parameters

string
The new status to assign to the issue. Valid values: “resolved”, “resolvedInNextRelease”, “unresolved”, “ignored”.
boolean
Updates if the user has seen the issue (true for seen, false for unseen).
boolean
Sets the issue’s visibility (true for public, false for private).
string
required
The unique identifier of the issue to be updated.
string
Actor ID (e.g., ‘user:1’, ‘team:2’), username, or email for assignment. Omit, or use an empty string or ‘null’ equivalent, to unassign.
boolean
Updates the user’s bookmark for the issue (true to bookmark, false to remove).
boolean
Updates the user’s notification subscription for the issue (true to subscribe, false to unsubscribe).
string
required
The unique identifier (ID) or slug of the Sentry organization.
string
The commit hash associated with the fix for this issue.
string
The Sentry release version in which the issue is considered resolved.
boolean
Specifies if the issue is resolved in the next Sentry release.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_MONITOR_FOR_PROJECTUpdates a monitor for a project. Use when you need to modify monitor name, schedule, check-in margin, max runtime, timezone, status, owner, or alert thresholds for a project-level monitor.

Input Parameters

string
required
Name of the monitor. Used for notifications. Required field.
string
Uniquely identifies your monitor within your organization. Changing this slug will require updates to any instrumented check-in calls. Must start with a lowercase letter and contain only lowercase letters, numbers, underscores, or hyphens.
string
The ID of the team or user that owns the monitor. Format: ‘user:51’ or ‘team:6’.
object
required
The configuration for the monitor including schedule, thresholds, and alert settings.
string ("active" | "disabled")
Status of the monitor. Disabled monitors will not accept events and will not count towards the monitor quota.
string
required
The project slug to associate the monitor to. Required field.
boolean
Disable creation of monitor incidents. Set to true to suppress alerts.
string
required
The ID or slug of the monitor to update.
string
required
The ID or slug of the project the resource belongs to.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_ORGANIZATION_ALERT_RULESReplaces an existing Sentry metric alert rule’s configuration; fields not provided in the request are removed or reset. This action updates an existing metric alert rule. Note that this is a full replacement - any fields not provided will be removed or reset to defaults. Prerequisites: - The organization must have metric alerts feature enabled - The alert_rule_id must be a valid existing metric alert rule - Use SENTRY_FETCH_ORGANIZATION_ALERT_RULES to get existing alert rule IDs

Input Parameters

string
required
Descriptive name for the alert rule.
string
Sentry actor ID (e.g., team:123, user:456) owning the rule, determining management permissions.
string
required
Sentry search query to filter events/metrics. An empty string ('') applies no filter.
string
Dataset to query (events, transactions, metrics, sessions, generic-metrics). Affects available fields/aggregations; see Sentry’s ‘Metric Alert Rule Types’ docs.
array
required
List of project slugs to scope the alert rule.
array
required
List of trigger configurations defining alert conditions (critical/warning labels, thresholds) and notification actions (e.g., email, Slack). critical label is mandatory. See Sentry API docs for full action schema.
string
required
Aggregate function for the metric (e.g., count, p95). See Sentry’s ‘Metric Alert Rule Types’ documentation for configurations based on dataset and query type.
integer
Query type, often related to dataset: 0 (error events), 1 (transaction events), 2 (none). See Sentry’s ‘Metric Alert Rule Types’ for valid combinations.
array
Specific event types for this alert (e.g., default, error, transaction).
integer
required
Time window in minutes for aggregate computation (1, 5, 10, 15, 30, 60, 120, 240, 1440).
string
Environment to filter events/metrics (e.g., ‘production’). If omitted, applies to all environments.
integer
Monitoring state of the rule (e.g., continuously active or conditionally activated via activationCondition).
integer
required
Unique numeric ID of the metric alert rule to update.
integer
required
Comparison operator for thresholds: 0 for ‘Above’ (metric > threshold) or ‘Higher than’ (percentage change), 1 for ‘Below’ (metric < threshold) or ‘Lower than’.
integer
Comparison period (minutes) for percentage change thresholds (e.g., ‘X% higher than Y minutes ago’). Required if thresholdType implies percentage change; not for ‘Crash Free…’ alerts.
integer
Metric value for alert resolution. If unspecified, derived from lowest severity trigger. If thresholdType is 0 (‘Above’), resolveThreshold must be < critical threshold to resolve when metric drops below this value; if 1 (‘Below’), it must be > critical threshold to resolve when metric rises above this value.
integer
Optional condition for rule activation, used with certain monitorType values.
string
required
Unique identifier (ID or slug) of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_ORGANIZATION_DASHBOARDUpdates an existing custom dashboard, allowing modifications to its title, widgets, and data filters; providing widgets, projects, environment, period, start, end, or filters will overwrite existing settings for those fields.

Input Parameters

string
Unique identifier for the dashboard; should match existing ID if updating.
string
The absolute end time for the dashboard’s time range, in ISO 8601 format (e.g., ‘2023-01-02T00:00:00Z’). If provided along with ‘start’, period is ignored. Replaces the existing end time.
boolean
A boolean indicating whether the dashboard’s time range should be displayed in UTC. True for UTC, False for the user’s local time.
string
The absolute start time for the dashboard’s time range, in ISO 8601 format (e.g., ‘2023-01-01T00:00:00Z’). If provided along with ‘end’, period is ignored. Replaces the existing start time.
string
The new title for the dashboard.
string
The relative time range period for the dashboard (e.g., ‘24h’, ‘7d’, ‘30d’). Replaces the existing period. If ‘start’ and ‘end’ are set, this is ignored.
object
A dictionary of additional filters to apply to the dashboard data, replacing existing filters. Keys are filter names, values are filter values.
array
A list of widget configurations to be updated or set for this dashboard. This will replace all existing widgets.
array
A list of project IDs to filter the dashboard data by. Replaces the existing project filter.
array
A list of environment names to filter the dashboard data by. Replaces the existing environment filter.
integer
required
The ID of the dashboard to be updated.
string
required
The ID or slug of the organization the resource belongs to.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_ORGANIZATION_MEMBER_ROLEUpdates a Sentry organization member’s organization-level role and team roles. The request sends an empty team roles list by default when team roles are omitted.

Input Parameters

string ("billing" | "member" | "manager" | "owner" | "admin")
Sets the member’s new organization-level role (e.g., ‘billing’ for payments, ‘member’ for event access, ‘manager’ for project/team admin, ‘owner’ for full control). The ‘admin’ role is not assignable on Business/Enterprise plans; use teamRoles for granular admin tasks.
string
required
The ID of the member whose roles are to be updated.
array
List of team role assignments (each object specifying teamSlug and role). This list completely replaces existing team roles. An empty list (default) removes the member from all teams. Team roles: contributor (views/acts on issues), admin (full team/project management).
string
required
The ID or slug of the organization to which the member belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_PROJECT_DETAILSUpdates a Sentry project’s settings (e.g., name, slug, platform, bookmark status); isBookmarked can be updated with project:read permission, other fields typically require project:write or project:admin permissions.

Input Parameters

string
The new name for the project.
string
The new unique identifier (slug) for the project, used in URLs and the Sentry interface.
string
The new platform for the project (e.g., python, javascript, java). This helps Sentry categorize and process errors.
integer
The duration in hours after which an issue is automatically resolved if it hasn’t been seen. Set to 0 to disable auto-resolution.
boolean
Toggles whether the project is starred (bookmarked) in the Sentry UI.
array
A list of tag keys (e.g., ‘release’, ‘environment’) to highlight on this project’s issues in Sentry’s UI. For example: ["release", "environment", "server_name"].
string
Custom prefix for the subject line of notification emails sent from this project.
string
The template for the email subject (excluding the prefix) for individual issue alerts. Available variables: $title, $shortID, $projectID, $orgID, and ${tag:key} (e.g., ${tag:environment}, ${tag:release}).
object
A JSON object mapping context types (e.g., ‘user’, ‘device’) to a list of their keys to be highlighted in Sentry’s UI for issues within this project. For example: {"user": ["id", "email"], "device": ["model"]}.
string
required
The ID or slug of the Sentry project to be updated.
string
required
The ID or slug of the Sentry organization to which the project belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_PROJECT_ISSUE_STATUS_AND_DETAILSBulk updates attributes of issues in a Sentry project, selecting issues by ID or status. If IDs are omitted when a status filter is used, the update targets all issues matching that status.

Input Parameters

array
Issue IDs to update. Accepts a list of integers for bulk updates. Optional; if omitted and the ‘status’ query parameter (filter) is used, updates all issues matching that status.
boolean
Set to true to merge issues, false to unmerge. If merging, ensure the target issue ID is correctly specified.
string
The new status to apply to the selected issues (request body parameter). Valid values are "resolved", "resolvedInNextRelease", "unresolved", and "ignored".
boolean
If called with user context: true to mark issue as seen by the user, false as unseen.
boolean
Set to true for public, false for private.
string
Actor ID (e.g., user:123 or team:456) or username for assignment. Use an empty string or null to unassign.
boolean
If called with user context: true to bookmark issue for the user, false to remove bookmark.
integer
Minutes to ignore this issue (alternative to statusDetails.ignoreDuration).
string
required
ID or slug of the Sentry project.
string
required
ID or slug of the Sentry organization.
string
Commit ID in which the issue is resolved.
string
Version/release in which the issue is resolved.
integer
Number of times to ignore the issue before it resurfaces.
integer
Time window (in minutes) for ignoreCount.
boolean
Indicates if the issue is resolved in the next release.
integer
Duration (in minutes) to ignore the issue.
integer
Number of unique users affected before a previously ignored issue resurfaces.
integer
Time window (in minutes) for ignoreUserCount.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_PROJECT_KEY_CONFIGURATIONUpdates configuration settings (e.g., name, status, rate limits, SDK options) for an existing Sentry client key (DSN), identified by key_id, within a specified project_id_or_slug and organization_id_or_slug.

Input Parameters

string
New human-readable name for the client key. Name will not be changed if omitted.
string
required
The ID of the client key (DSN public key) to be updated.
boolean
Specifies if the client key should be active (true to activate, false to deactivate). Status remains unchanged if omitted.
integer
Maximum number of events the key can accept within rateLimit_window. Uses existing settings or project defaults if omitted.
string ("latest" | "10.x" | "9.x" | "8.x" | "7.x")
Sentry JavaScript SDK version for the loader (‘latest’, ‘10.x’, ‘9.x’, ‘8.x’, or ‘7.x’). Current setting remains unchanged if omitted.
integer
Time window in seconds for rateLimit_count (e.g., 3600 for 1 hour). Uses existing settings or project defaults if omitted.
string
required
The unique identifier (ID or slug) of the Sentry project whose key is being updated.
string
required
The unique identifier (ID or slug) of the Sentry organization to which the project belongs.
boolean
Enable (true) or disable (false) Debugging features for the dynamic SDK loader. Current setting remains unchanged if omitted.
boolean
Enable (true) or disable (false) Session Replay for the dynamic SDK loader. Current setting remains unchanged if omitted.
boolean
Enable (true) or disable (false) Performance Monitoring for the dynamic SDK loader. Current setting remains unchanged if omitted.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_PROJECT_OWNERSHIP_SETTINGSUpdates a Sentry project’s ownership settings, including raw rules, fallthrough, auto-assignment and CODEOWNERS sync. CODEOWNERS sync defaults to enabled when omitted.

Input Parameters

string
Raw Sentry ownership rule string (e.g., ‘path:src/components/* #frontend’) defining issue assignment based on file paths or URLs. See Sentry’s Ownership Rules documentation for syntax.
boolean
If True, assigns issues to all project members if no ownership rule matches; if False, no owners are set by default in such cases.
string
Strategy for assigning new issues not covered by ownership rules. Options: ‘Auto Assign to Issue Owner’, ‘Auto Assign to Suspect Commits’, ‘Turn off Auto-Assignment’.
boolean
If True (default), automatically synchronizes Sentry issue ownership with the repository’s CODEOWNERS file during a release.
string
required
The ID or slug of the Sentry project.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_PROJECT_RELEASE_FILE_DETAILSUpdates the name (path) or distribution identifier of a specific file within an existing project release in Sentry.

Input Parameters

string
The new distribution identifier for the file. Used to distinguish different builds of the same release version (e.g., build numbers or commit SHAs). WARNING: The Sentry API may not reliably update this field via the PUT endpoint; the ‘name’ parameter updates successfully but ‘dist’ may remain unchanged. At least one of ‘name’ or ‘dist’ must be provided.
string
The new name or full path for the file. Use absolute paths (e.g., ’~/dist/main.js’) or URLs (e.g., ‘https://example.com/app.js’). At least one of ‘name’ or ‘dist’ must be provided.
string
required
The unique identifier of the release file to be updated.
string
required
The version identifier of the release, e.g., ‘1.0.0’ or ‘my-app@2.3.1’.
string
required
The ID or slug of the project associated with the release file.
string
required
The ID or slug of the organization to which the project belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_PROJECT_RULE_BY_IDUpdates an existing Sentry project issue alert rule by ID. Omitted fields may be cleared or reset to defaults.

Input Parameters

string
required
The new name for the alert rule.
string
The ID of the team or user that owns this rule. Format: team:TEAM_ID or user:USER_ID or the user’s email, or a team name prefixed with ’#’. For example, ‘user@example.com’ or ‘#platform-team’.
array
required
Actions performed when rule conditions and filters are met. Structure varies by action type chosen; refer to Sentry’s issue alert rule documentation.
array
Optional filters refining when the rule fires after conditions are met. Structure varies by filter type chosen; refer to Sentry’s issue alert rule documentation.
integer
required
The numeric ID of the alert rule to be updated.
integer
required
The minimum interval, in minutes, between actions for the same issue. Valid range is 5 to 43200 (30 days).
array
required
Conditions that trigger the rule. Structure varies by condition type chosen; refer to Sentry’s issue alert rule documentation.
string ("all" | "any")
required
Specifies how conditions must align for actions: ‘all’ (all true), ‘any’ (at least one true), or ‘none’ (all false).
string
Specific environment for this rule (e.g., ‘production’); applies to all environments if omitted.
string ("all" | "any" | "none")
Specifies how filters (if any) must align for actions: ‘all’ (all true), ‘any’ (at least one true), or ‘none’ (all false).
string
required
The unique identifier (ID) or human-readable slug of the Sentry project.
string
required
The unique identifier (ID) or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_RELEASE_DETAILS_FOR_ORGANIZATIONUpdates an existing Sentry release’s details for an organization, including its reference, URL, release date, associated commits, or repository references.

Input Parameters

string
Commit reference (e.g., a branch name, tag, or commit SHA) to associate with this release; useful if a tagged version has been provided.
string
A URL that points to the release. For instance, this can be the path to an online interface to the source code, such as a GitHub URL, or a link to a release announcement.
array
Indicates or updates the start and end commits for each repository in a release. Head commits require repository and commit (HEAD SHA), and can optionally include previousCommit (SHA of previous release’s HEAD) for initial data sends or corrections.
array
List of commit data to associate or update for this release; can add new commits or modify existing ones if Sentry’s commit tracking needs adjustment.
string
required
The version identifier of the release to be updated (e.g., ‘1.0.0’, ‘my-project@2.3.12’). This identifier must be unique within the organization.
string
ISO 8601 timestamp indicating when the release went live (e.g., ‘2023-10-26T10:00:00Z’). If not provided, Sentry uses the current time, but an existing dateReleased will not be overwritten unless a new value is provided.
string
required
The unique ID or human-readable slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_SAVED_QUERY_FOR_ORGANIZATIONUpdates an existing Discover saved query for a Sentry organization. If omitted, projects is sent as an empty list and the query dataset as error-events.

Input Parameters

string
The specific end date and time for the query’s time range, in ISO 8601 format (e.g., ‘2023-01-31T23:59:59Z’); used if ‘range’ is not provided.
string
required
The new user-defined name for the saved query.
string
The Sentry search query string to filter results (e.g., ‘error.type:ZeroDivisionError browser.name:Firefox’). Refer to Sentry’s search syntax documentation for details.
string
The relative time range period for this saved query (e.g., ‘24h’, ‘7d’, ‘30d’); an alternative to specific ‘start’ and ‘end’ times.
string
The specific start date and time for the query’s time range, in ISO 8601 format (e.g., ‘2023-01-01T00:00:00Z’); used if ‘range’ is not provided.
array
A list of aggregate functions to be plotted on the Y-axis of the chart (e.g., ‘count()’, ‘p95(transaction.duration)’).
array
A list of fields, functions, or equations for the query, with a maximum of 20. Each item can be: 1. A built-in key field (e.g., ‘transaction’; see Sentry’s properties table for event properties). 2. A tag, formatted as ‘tag[tagName]’ (e.g., ‘tag[isEnterprise]’). 3. A function, like ‘function_name(parameters,…)’ (e.g., ‘count_if(transaction.duration,greater,300)’; Discover groups by tags/fields when functions are used; see Sentry’s query builder documentation). 4. An equation, prefixed with ‘equation|’ (e.g., ‘equation|count_if(transaction.duration,greater,300) / count() * 100’; see Sentry’s documentation on query equations).
string
The visualization type for the saved query chart. Allowed values are: ‘default’, ‘previous’, ‘top5’, ‘daily’, ‘dailytop5’, ‘bar’.
string
Field to sort the query results by. Must be one of the items in the ‘fields’ list (excluding equations). Prefix with a hyphen ’-’ for descending order (e.g., ‘-count()’).
string
The resolution of the time series for the chart (e.g., ‘1h’, ‘1d’, ‘30m’).
array
A list of project IDs to associate with this saved query. An empty list means the query applies to all projects selected in the Sentry UI unless overridden.
integer
required
The unique identifier of the Discover saved query to be updated.
integer
The number of top events’ timeseries to be visualized on the chart.
array
A list of environment names to filter the query by.
string ("discover" | "error-events" | "transaction-like")
The dataset to query. Note: ‘discover’ is deprecated; use ‘error-events’ or ‘transaction-like’ instead.
string
required
The ID or slug of the Sentry organization to which the saved query belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_TEAM_INFORMATION_BY_ORGANIZATION_IDUpdates the slug for an existing team within a Sentry organization.

Input Parameters

string
required
The new slug for the team. Must be unique within the organization and follow the pattern: starts with a lowercase letter, followed by lowercase letters, numbers, underscores, or hyphens.
string
required
The unique identifier (ID or slug) of the team whose slug is to be updated.
string
required
The unique identifier (ID or slug) of the organization to which the team belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_USER_EMAILUpdates the primary email address for a Sentry user. The new email must already be added as a secondary email and be verified. AUTHENTICATION REQUIREMENTS: - Requires user:write scope - Typically requires a PERSONAL auth token (created from User Settings > Personal Tokens) - Internal integration tokens (organization-scoped) may not have permission for user-level operations PREREQUISITES: - The new email must already be added to the user’s account as a secondary email - The email must be verified before it can be set as primary COMMON ERRORS: - 403 Forbidden: Token lacks user:write scope or is not a personal auth token - 400 Bad Request: Email is not already added to the account or is not verified

Input Parameters

string
required
The new primary email address to set for the user. This email must already be added as a secondary email to the user’s account and be verified before it can be set as primary. The email must be in valid format (e.g., user@example.com).
string
required
The unique identifier of the Sentry user whose primary email address is to be updated. Can be the numerical user ID or ‘me’ for the authenticated user. NOTE: This endpoint requires user:write scope and typically requires a personal auth token (from User Settings > Personal Tokens) rather than an integration token.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPDATE_WEBHOOK_CONFIGURATION_XPUpdates an existing Sentry service hook’s target URL and subscribed event types for a given project and organization. Service hooks (webhooks) are HTTP callbacks that notify external systems when specific events occur in Sentry. This action allows you to modify the webhook’s URL and change which events trigger notifications. Valid event types are: - ‘event.alert’: Triggered when alerts fire - ‘event.created’: Triggered when new events are processed Requirements: - Authentication with ‘project:write’ scope - The ‘servicehooks’ feature must be enabled for your Sentry plan - The hook_id must be a valid GUID from an existing service hook Common use cases: - Updating webhook URL when your endpoint changes - Modifying event subscriptions to receive different notification types - Reconfiguring webhooks for testing or production environments

Input Parameters

string
required
The URL to which Sentry will send webhook POST requests when subscribed events occur.
array
required
A list of Sentry event types to subscribe to. Valid event types are: ‘event.alert’ (triggered when alerts fire) and ‘event.created’ (triggered when new events are processed).
string
required
The unique identifier (GUID) of the service hook to be updated.
string
required
The ID or slug of the project to which the service hook belongs.
string
required
The ID or slug of the organization to which the service hook belongs.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPLOAD_DSYMS_FILE_TO_PROJECTUploads a dSYM (debug symbols) zip archive, containing an Apple .dSYM folder, to the specified Sentry project for symbolicating crash reports from Apple platforms.

Input Parameters

object
The dSYM file to upload, provided as a zip archive of an Apple .dSYM folder containing debug symbols.
string
required
Unique ID or slug of the Sentry project.
string
required
Unique ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPLOAD_FILE_TO_PROJECT_RELEASEUploads a file to a Sentry project release, for an existing organization, project, and version; uses multipart/form-data and the region-specific Sentry domain.

Input Parameters

string
Optional: Distribution identifier to distinguish multiple files of the same name within a single release (e.g., for different build variants or AB tests).
object
The file to be uploaded.
string
Optional: Name for the file, ideally an absolute path or URI (e.g., for JavaScript source maps, the full web URI to the original ‘.js’ file).
string
Optional: Header for the file, formatted as ‘Header-Key: Header-Value’ (e.g., ‘X-SourceMap:/url/to/sourcemap.map’ for SourceMap debug images).
string
required
The version identifier of the release to associate the file with.
string
required
The ID or slug of the Sentry project.
string
required
The ID or slug of the Sentry organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_UPLOAD_RELEASE_FILE_TO_ORGANIZATIONUploads a new file, such as a source map or debug information, to an existing release version in a Sentry organization.

Input Parameters

string
An optional distribution identifier for the file. This helps differentiate between multiple files with the same name within a single release, often used for build numbers or variant identifiers (e.g., Android versionCode or Xcode build number).
object
The file to be uploaded for the release.
string
The optional name of the file, which should reflect the absolute path or URI where this file will be referenced. For example, for JavaScript source maps, this could be the full web URI.
string
An optional header string or list of strings to be associated with the artifact. This can be used to specify headers like ‘Content-Type’ or custom metadata. For example: ‘Content-Type:application/json’ or [‘X-SourceMap: /url/to/source.map’, ‘Content-Type: application/json’].
string
required
The version identifier of the release.
string
required
The ID or slug of the organization.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_VALIDATE_CREDENTIALValidates Sentry API credentials by retrieving the authenticated user’s profile. Authentication token details, including scopes and expiration, may also be returned.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not
Slug: SENTRY_VIEW_ORGANIZATION_NOTIFICATION_ACTIONSRetrieves Spike Protection notification actions for a Sentry organization, filterable by project IDs or slugs (slugs take precedence); if triggerType is used, it must be ‘spike-protection’.

Input Parameters

array
List of project IDs to filter notification actions. Use [-1] for all projects. project_id_or_slug takes precedence if also provided.
string
Filters actions by trigger type. Currently, only ‘spike-protection’ is supported.
array
List of project slugs to filter notification actions. Use ["$all"] for all projects. Takes precedence over project if also specified.
string
required
The unique ID or slug of the Sentry organization for which to view notification actions.

Output

string
required
Data from the action execution
string
Error if any occurred during the execution of the action
boolean
required
Whether or not the action execution was successful or not