Slack

1. What you get with Slack
2. How the integration works
3. Good to know

Slack is where engineering teams already live, and deployment news belongs where people will actually see it. Connect Slack to Rocketeers and deploys, build results, uptime changes and incidents arrive in the channel of your choice — no dashboard-checking, no "did it deploy?" messages in DMs.

#What you get with Slack

• Deploy and build notifications the moment they happen, in the channel you pick.
• Uptime and incident alerts, so an outage pings the team before a customer does.
• Per-channel routing: production alerts in #ops, staging chatter somewhere quieter.
• Simple webhook setup — running in minutes, no bot user to host or maintain.
• The whole team informed without anyone changing how they work.

#How the integration works

Create an incoming webhook for your workspace — Slack issues a unique URL tied to a specific channel — and paste it into Rocketeers. From then on, Rocketeers posts notifications to that URL: deployments starting and finishing, builds failing, sites going down and coming back up. Want different events in different channels? Create a webhook per channel and point each notification type where it belongs.

#Good to know

• Incoming webhooks are created through a Slack app; depending on workspace settings, an admin may need to approve the app before webhooks can be added.
• Each webhook URL posts to exactly one channel — the channel is fixed when the webhook is created.
• Webhook URLs are secrets: anyone holding one can post to your channel, so treat them like credentials and rotate them if leaked.
• Slack rate-limits incoming webhooks to roughly one message per second, which normal deploy and alert traffic never approaches.
• Free Slack workspaces work fine — incoming webhooks don't require a paid plan.