Slack Incident Response — AI Bot Template for Internal
Bot
Slack incident response bot. Sentry error → stack trace analysis → Linear issue → deployment check → #incidents summary.
Template Slack Incident Response bundles a ready-to-deploy workspace for internal workflows. Install in one click from the Aerostack dashboard or via aerostack init --template=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
Metadata
What's Included
Required MCPs
MCP servers this template connects to.
Tags
Deploy this bot in minutes
Slack incident response bot. Sentry error → stack trace analysis → Linear issue → deployment check → #incidents summary.
More internal Templates
Browse internal Templates →Slack DevOps Deploy Bot
by @aerostack
Slack DevOps deploy bot. Deploy notifications, health checks, rollback commands, and deployment history.
Slack HR & People Ops
by @aerostack
Slack HR and people ops bot. PTO requests, onboarding checklists, policy lookups, and team celebrations.
Telegram Team Standup
by @aerostack
Telegram team standup bot. Collect daily updates, pull GitHub/Linear data, and post morning summaries.
Slack Weekly Report Generator
by @aerostack
Slack weekly report bot. Auto-generate team reports from GitHub, Linear, and PostHog data — posted every Friday.
HR & Employee Onboarding
by @aerostack
HR and onboarding bot. Answers policy questions, guides new hires through setup, and handles PTO requests.
IT Helpdesk
by @aerostack
IT helpdesk bot. Password resets, software access, device troubleshooting — with ticket creation.
Frequently asked questions
What does the Slack Incident Response bot automate from alert to resolution?+
It receives a Sentry error, analyzes the stack trace, creates a Linear issue, checks the latest Railway deployment, and posts a structured summary to your #incidents channel automatically.
Which MCPs are wired into the Slack Incident Response template?+
@aerostack/mcp-slack for channel posting, @aerostack/mcp-sentry for error ingestion, @aerostack/mcp-github for commit context, @aerostack/mcp-linear for issue creation, and @aerostack/mcp-railway for deployment checks.
How do I change which Slack channel or Linear team the incident bot targets?+
Update the channel name and Linear team ID in the workspace agent config. Each MCP scope is independently adjustable, so you can route critical vs. low-priority incidents to different channels.
Is the Slack Incident Response bot suitable for small engineering teams?+
Yes. It requires Sentry, Linear, and Railway accounts plus a Slack workspace. Teams without all five MCPs can disable unused ones; the bot degrades gracefully to the connected tools.