sentry-create-alert

Q: How do I install sentry-create-alert?

Run npx skills add https://github.com/getsentry/plugin-claude --skill sentry-create-alert in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sentry-create-alert/ (personal) or .claude/skills/sentry-create-alert/ (project).

by getsentryDevOps & Cloud

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.

Installs: 60
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/getsentry/plugin-claude --skill sentry-create-alert

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads sentry-create-alert automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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.

API="https://{region}.sentry.io/api/0/organizations/{org}"
AUTH="Authorization: Bearer {token}"

# Find user ID by email
curl -s "$API/members/" -H "$AUTH" | python3 -c "
import json,sys
for m in json.load(sys.stdin):
  if m.get('email')=='USER_EMAIL' or m.get('user',{}).get('email')=='USER_EMAIL':
    print(m['user']['id']); break"

# List teams
curl -s "$API/teams/" -H "$AUTH" | python3 -c "
import json,sys
for t in json.load(sys.stdin):
  print(t['id'], t['slug'])"

# List integrations (for Slack/PagerDuty)
curl -s "$API/integrations/" -H "$AUTH" | python3 -c "
import json,sys
for i in json.load(sys.stdin):
  print(i['id'], i['provider']['key'], i['name'])"

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, 10=Outage: uptime and cron)
`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

{
  "name": "<Alert Name>",
  "enabled": true,
  "environment": null,
  "config": { "frequency": 30 },
  "triggers": {
    "logicType": "any-short",
    "conditions": [
      { "type": "first_seen_event", "comparison": true, "conditionResult": true }
    ],
    "actions": []
  },
  "actionFilters": [{
    "logicType": "all",
    "conditions": [
      { "type": "issue_priority_greater_or_equal", "comparison": 75, "conditionResult": true },
      { "type": "event_frequency_count", "comparison": {"value": 50, "interval": "1hr"}, "conditionResult": true }
    ],
    "actions": [{
      "type": "email",
      "integrationId": null,
      "data": {},
      "config": {
        "targetType": "user",
        "targetIdentifier": "<user_id>",
        "targetDisplay": null
      },
      "status": "active"
    }]
  }]
}

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

curl -s -w "\n%{http_code}" -X POST \
  "https://{region}.sentry.io/api/0/organizations/{org}/workflows/" \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{payload}'

Expect HTTP 201. The response contains the workflow id.

Phase 5: Verify

Confirm the alert was created and provide the UI link:

https://{org_slug}.sentry.io/monitors/alerts/{workflow_id}/

If the org lacks the workflow-engine-ui feature flag, the alert appears at:

https://{org_slug}.sentry.io/alerts/rules/

Managing Alerts

# List all workflows
curl -s "$API/workflows/" -H "$AUTH"

# Get one workflow
curl -s "$API/workflows/{id}/" -H "$AUTH"

# Update a workflow
curl -s -X PUT "$API/workflows/{id}/" -H "$AUTH" -H "Content-Type: application/json" -d '{payload}'

# Delete a workflow
curl -s -X DELETE "$API/workflows/{id}/" -H "$AUTH"
# Expect 204

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

FAQ

What does the sentry-create-alert skill do?

How do I install sentry-create-alert?

Run npx skills add https://github.com/getsentry/plugin-claude --skill sentry-create-alert in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sentry-create-alert/ (personal) or .claude/skills/sentry-create-alert/ (project).

Which AI agents can use sentry-create-alert?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is sentry-create-alert safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains sentry-create-alert?

It is published by getsentry in getsentry/plugin-claude. It has 60 recorded installs.

More from getsentry/plugin-claude

View all →

sentry-debug-issue

getsentry/plugin-claude

Debug and fix a Sentry issue — find it (by link, ID, or search), pull full context (stack trace, breadcrumbs, trace, logs), optionally run Seer root-cause / autofix, apply the code fix, and resolve it via a Fixes PROJECT-NAME-12A commit/PR. Use when working a known error or hunting one down to fix.

Code Quality & Workflow68 installs