Runner.Rank issues by user impact
“Show me unresolved Sentry issues sorted by the number of affected users.”
Error triage starts from impact data instead of most-recent-first noise.
Sentry Runner Workflows
Monitor errors, triage issues by impact, and keep production health visible in the workflow.
SentryObservability
+New Session
Sessions
Connected appsSentry
GitHub
Linear
Slack
SentryGitHubLinearSlack+
Connect a new appWhat would you like to do?
Popular workflows with Sentry
Real workflow pages where Sentry is part of the connected stack. Each workflow shows the trigger, connectors, and outcome.
Weekly engineering pulse check
Engineering Sprint and Deploy Review
Engineering updates are grounded in data instead of ad-hoc Slack check-ins.
LinearGitHubSentrySlackProduction incident triage and response
Application Monitoring and Incident Response
Incident triage starts with context instead of a scramble across monitoring tools.
Logfire
SupabaseSentrySlackTriggers and actions
What Runner can do with Sentry. These are grounded in the real backend connector definitions, not generic marketing filler.
Fetch the stack trace for a specific error
“Pull the full stack trace and breadcrumbs for the auth timeout issue.”
Runner brings debugging context into the workflow before the engineering sync.
Check production health before the release
“Are there any new unresolved issues since the last deploy?”
Release decisions are grounded in real error data, not gut feel.
Compare error rates across releases
“How does the error rate in this release compare to last week?”
Release quality becomes a trend, not a point-in-time snapshot.
Use Sentry inside a real workflow
Download Runner to connect Sentry to the rest of your workflow instead of treating it like another isolated tab.