Slack Incident Response

What It Does

Automated incident response in Slack. When Sentry fires an error alert, the bot grabs the full stack trace, searches GitHub for the affected file and recent commits, checks Railway deployment logs, creates a Linear issue with all context, and posts a structured summary to #incidents.

From alert to actionable incident ticket in under 30 seconds.

What's Built In

• Error analysis — pulls full Sentry event: stack trace, affected users count, first/last seen timestamps
• Code context — searches GitHub for the file in the stack trace and finds recent commits that may have introduced the bug
• Deployment correlation — checks Railway logs for the time window of the error
• Ticket creation — creates a Linear issue with stack trace, affected users, recent commits, and suggested priority
• Incident summary — posts a formatted summary to #incidents with error, impact, source file, last commit author, and suggested owner

Best For

• Engineering teams with 5+ developers shipping daily where incident response time matters
• On-call rotations that need structured incident context instead of raw Sentry alerts
• Teams using Sentry + GitHub + Linear that want their incident workflow automated end-to-end