Notification integrations
Connect email and Slack destinations for run and issue events.
Notification integrations route operational events to the right team surfaces.
Use email targets for release owners, QA leads, or shared team aliases. Each email target must include at least one valid address.
Slack
Use Slack targets for channels where run failures and issue activity are reviewed. Killbug sends Slack notifications through a Slack incoming webhook URL.
Create an incoming webhook URL
- Open the Slack app management dashboard.
- Create a Slack app, or select an existing app owned by your workspace.
- In the app settings, open Incoming Webhooks.
- Turn Activate Incoming Webhooks on.
- Select Add New Webhook to Workspace.
- Choose the channel where Killbug should post notifications, then authorize the app.
- Copy the generated webhook URL from Webhook URLs for Your Workspace. It should look like
https://hooks.slack.com/services/.... - Paste that URL into the Slack Webhook URL field in Killbug and save the notification.
If the target is a private Slack channel, join that channel before adding the webhook.
Security
Treat the Slack webhook URL like a secret. Anyone with the URL can post messages to the selected channel. Store it only in Killbug or trusted secret stores, and rotate it if it is exposed or if channel ownership changes.
For GovSlack workspaces, Slack uses the slack-gov.com domain instead of slack.com.
Event design
Create channels by responsibility:
- Release channel: failed run results and high-priority issues.
- QA channel: new issues and issue resolution.
- Owner channel: scheduled plan failures for a specific product area.
Avoid routing every event to every destination. Notification fatigue makes regression evidence easier to ignore.