Slack DevOps Deploy Bot — AI Bot Template for Internal
Bot
Slack DevOps deploy bot. Deploy notifications, health checks, rollback commands, and deployment history.
Template Slack DevOps Deploy Bot bundles a ready-to-deploy workspace for internal workflows.
Install in one click from the Aerostack dashboard or via aerostack init --template=slack-devops-deploy-bot.
What It Does
DevOps operations from Slack. Get deploy notifications, run health checks, trigger rollbacks, and view deployment history — all without leaving your messaging app. Connects to GitHub for CI/CD, Railway for hosting, and Sentry for error monitoring.
What's Built In
- Deploy notifications — automatic messages when deployments succeed or fail, with commit details
- Health checks — run service health checks on demand and get formatted status reports
- Rollback commands — trigger rollbacks from Slack with confirmation prompts and audit logging
- Deployment history — view recent deployments, their status, and who triggered them
- Error correlation — after a deploy, checks Sentry for any error spikes in the affected services
Best For
- Engineering teams that deploy multiple times per day and need deployment awareness without dashboard-hopping
- On-call engineers who need to check service health and rollback from their phone
- DevOps teams standardizing deployment workflows across the organization
psychology System Prompt
The instructions that define how this bot behaves. It ships pre-configured — edit it anytime in your workspace.
You are a DevOps deployment bot in Slack. ## DEPLOYMENT NOTIFICATIONS When a deployment starts/completes (via GitHub webhook or Railway): Post to #deployments: "DEPLOY [status] Service: [service name] Branch: [branch] → [environment] Commit: [short hash] — [commit message] Author: @[deployer] Duration: [X seconds] [Link to deployment]" ## HEALTH CHECKS After deployment: 1. Wait 60 seconds for the service to stabilize 2. Check Railway deployment health 3. Check Sentry for new errors in the 5-minute window after deploy 4. If new errors detected: post warning with error details 5. If healthy: post green confirmation ## ROLLBACK When someone says "rollback [service]": 1. Confirm: "Are you sure you want to rollback [service] to the previous deployment? Reply YES to confirm" 2. On confirmation: trigger rollback via Railway 3. Post: "Rollback initiated for [service]. Previous version deploying..." 4. Monitor health after rollback ## DEPLOYMENT HISTORY When asked "show deploys" or "deploy history": - Pull last 10 deployments from Railway - Show: date, service, status, author, duration ## PR MERGE TO DEPLOY TRACKING - When a PR is merged to main: post "PR #[number] merged. Deploy to staging expected in ~[X] minutes" - Track the deployment pipeline progress - Alert if deploy fails after merge ## RULES - NEVER auto-deploy to production — always require human confirmation - Rollback requires explicit YES confirmation - For production rollbacks: also notify #engineering-leads - Log all deployment actions with who triggered them ## TONE - Technical, precise, structured - Clear status indicators - No unnecessary commentary — just the facts - Urgent but calm for failures
checklist Setup Guide
Setup Guide — Slack DevOps Deploy Bot
Step 1: Slack App
- Create app with scopes:
chat:write,channels:read,channels:history - Install, copy Bot Token
- Create channels: #deployments, #engineering-leads
Step 2: GitHub
- Create token with
repoandactionsscopes - Set up webhook for push/deployment events
Step 3: Railway
- Create API token from Account Settings
Step 4: Sentry
- Create internal integration with
event:readscope
Step 5: Test
- Push a commit to your main branch
- Verify deploy notification appears in #deployments
Metadata
What's Included
Required MCPs
MCP servers this template connects to.
Tags
Deploy this bot in minutes
Slack DevOps deploy bot. Deploy notifications, health checks, rollback commands, and deployment history.
More Internal Templates
Browse Internal Templates →Slack Incident Response
by @aerostack
Slack incident response bot. Sentry error → stack trace analysis → Linear issue → deployment check → #incidents summary.
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 DevOps operations can the Slack DevOps Deploy Bot handle directly from Slack? +
It posts deployment notifications, runs health checks against Railway, surfaces Sentry error spikes post-deploy, accepts rollback commands, and returns a formatted deployment history on request.
Which MCPs are included in the Slack DevOps Deploy Bot template? +
@aerostack/mcp-slack for command handling and notifications, @aerostack/mcp-github for commit and PR context, @aerostack/mcp-railway for deployment triggers and health checks, and @aerostack/mcp-sentry for error-rate monitoring.
How do I add a new deployment environment to the Slack DevOps Deploy Bot? +
Add the environment's Railway service ID in the workspace config and create a corresponding Slack channel mapping. The bot will route deploy notifications and rollback commands per environment.
What teams benefit from the Slack DevOps Deploy Bot and what permissions are required? +
Engineering teams deploying to Railway who want deploy awareness in Slack without context-switching. Requires Slack bot scopes for message posting, Railway API token, GitHub token, and Sentry DSN.