Integrations
Forward issue alerts to Discord, Slack, or any HTTP endpoint.
Overview
Integrations let you send real-time notifications to external services whenever issues are created, resolved, reopened, or receive new events. booboo.dev supports three provider types:
- Discord — sends rich embeds to a Discord channel
- Slack — sends Block Kit messages to a Slack channel
- Custom Webhook — sends a signed JSON payload to any HTTPS endpoint
Integrations are configured at the organization level in Organization Settings and then routed to specific projects via routing rules.
Discord
Send issue alerts as rich embeds to a Discord channel.
Setup
- In Discord, right-click the channel you want alerts in and select Edit Channel
- Go to Integrations → Webhooks → New Webhook
- Give it a name (e.g. "booboo.dev") and click Copy Webhook URL
- In booboo.dev, go to Organization Settings and click Add Integration
- Select Discord, enter a name, and paste the webhook URL
- Click Create
What the messages look like
Discord messages appear as an embed with the booboo cyan accent color. The embed includes:
- Title — the issue ID and error message (e.g.
BACK-42: ZeroDivisionError: division by zero), linked to the issue in the dashboard - Project — the project name
- Culprit — the source file and function where the error occurred
- First seen — when the error first appeared
Slack
Send issue alerts as Block Kit messages to a Slack channel.
Setup
- Go to api.slack.com/apps and select your app (or create a new one)
- Navigate to Incoming Webhooks and toggle it on
- Click Add New Webhook to Workspace and select the channel
- Copy the webhook URL (starts with
https://hooks.slack.com/services/...) - In booboo.dev, go to Organization Settings and click Add Integration
- Select Slack, enter a name, and paste the webhook URL
- Click Create
What the messages look like
Slack messages use the Block Kit format with:
- Title — a clickable link with the issue ID and error message
- Context line — project name, culprit, and first-seen timestamp
- Accent color — booboo cyan sidebar
Custom Webhook
Send a signed JSON payload to any HTTPS endpoint. Use this for custom integrations with PagerDuty, OpsGenie, your own alerting system, or any service that accepts webhooks.
Setup
- In booboo.dev, go to Organization Settings and click Add Integration
- Select Webhook, enter a name, and enter your endpoint URL
- Click Create
- Copy the webhook secret that is displayed — it is shown only once and cannot be retrieved later
For payload format, signature verification, and full code examples, see the Webhook Payloads documentation.
Testing
Use the Test button next to any integration in Organization Settings to send a test payload and confirm your endpoint is working correctly.
Routing Rules
Routing rules control which projects trigger which integrations. By default, a newly created integration doesn't send alerts for any project — you need to create rules to connect them.
How it works
- Go to Project Settings for the project you want to configure
- Under the Integration Rules section, you'll see all integrations for your organization
- Use the master toggle to enable an integration for the project (all event types enabled by default)
- Use the per-event-type sub-toggles to control exactly which events trigger notifications
Each rule links one integration to one project for a specific event type (issue_created, issue_resolved, issue_reopened, or event_received).
Example
If you have a "Discord #backend-errors" integration and a "Slack #all-errors" integration, you could:
- Route only the Backend project to the Discord integration
- Route all projects to the Slack integration
When a new issue is created in the Backend project, both integrations fire. When a new issue is created in the Frontend project, only the Slack integration fires. Each integration can be configured to notify on specific event types per project.