Create Sentry alerts using the workflow engine API. Use when asked to create alerts, set up notifications, configure issue priority alerts, or build workflow automations. Supports email, Slack, PagerDuty, Discord, and other notification actions.

Create Sentry Alert Create alerts via Sentry's workflow engine API. Note: This API is currently in beta and may be subject to change. It is part of New Monitors and Alerts and may not be viewable in the legacy Alerts UI. Invoke This Skill When User asks to "create a Sentry alert" or "set up notifications" User wants to be emailed or notified when issues match certain conditions User mentions priority alerts, de escalation alerts, or workflow automations User wants to configure Slack, PagerDuty, or email notifications for Sentry issues Prerequisites curl available in shell Sentry org auth token with alerts:write scope (also accepts org:admin or org:write ) Phase 1: Gather Configuration Ask the user for any missing details: Detail Required Example Org slug Yes sentry , my org Auth token Yes sntryu ... (needs alerts:write scope) Region Yes (default: us ) us → us.sentry.io , de → de.sentry.io Alert name Yes "High Priority De escalation Alert" Trigger events Yes Which issue events fire the workflow Conditions Optional Filter conditions before actions execute Action type Yes email , slack , or pagerduty Action target Yes User email, team, channel, or service Phase 2: Look Up IDs Use these API calls to resolve names to IDs as needed. Phase 3: Build Payload Trigger Events Pick which issue events fire the workflow. Use logicType: "any short" (triggers must always use this). Type Fires when first seen event New issue created regression event Resolved issue recurs reappeared event Archived issue reappears issue resolved trigger Issue is resolved Filter Conditions Conditions that must pass before actions execute. Use logicType: "all" , "any short" , or "none" . The comparison field is polymorphic — its shape depends on the condition type : Type comparison format Description issue priority greater or equal 75 (bare integer) Priority = Low(25)/Medium(50)/High(75) issue priority deescalating true (bare boolean) Priority dropped below peak event frequency count {"value": 100, "interval": "1hr"} Event count in time window event unique user frequency count {"value": 50, "interval": "1hr"} Affected users in time window tagged event {"key": "level", "match": "eq", "value": "error"} Event tag matches assigned to {"targetType": "Member", "targetIdentifier": 123} Issue assigned to target level {"level": 40, "match": "gte"} Event level (fatal=50, error=40, warning=30) age comparison {"time": "hour", "value": 24, "comparisonType": "older"} Issue age issue category {"value": 1} Category (1=Error, 6=Feedback) issue occurrences {"value": 100} Total occurrence count Interval options: "1min" , "5min" , "15min" , "1hr" , "1d" , "1w" , "30d" Tag match types: "co" (contains), "nc" (not contains), "eq" , "ne" , "sw" (starts with), "ew" (ends with), "is" (set), "ns" (not set) Set conditionResult to false to invert (fire when condition is NOT met). Actions Type Key Config email config.targetType : "user" / "team" / "issue owners" , config.targetIdentifier : <id slack integrationId : <id , config.targetDisplay : " channel name" pagerduty integrationId : <id , config.targetDisplay : <service name , data.priority : "critical" discord integrationId : <id , data.tags : tag list msteams integrationId : <id , config.targetDisplay : <channel opsgenie integrationId : <id , data.priority : "P1" "P5" jira integrationId : <id , data : project/issue config github integrationId : <id , data : repo/issue config Full Payload Structure frequency : minutes between repeated notifications. Allowed values: 0 , 5 , 10 , 30 , 60 , 180 , 720 , 1440 . Structure note: triggers.actions is always [] — actions live inside actionFilters[].actions . Phase 4: Create the Alert Expect HTTP 201 . The response contains the workflow id . Phase 5: Verify Confirm the alert was created and provide the UI link: If the org lacks the workflow engine ui feature flag, the alert appears at: Managing Alerts Troubleshooting Issue Solution 401 Unauthorized Token needs alerts:write scope 403 Forbidden Token must belong to the target org 404 Not Found Check org slug and region ( us vs de ) 400 Bad Request Validate payload JSON structure, check required fields User ID not found Verify email matches a member of the org

sentry-create-alert