Slack

bichito ships a Slack transform that re-shapes the webhook payload into Slack's incoming-webhook format. Paste a Slack URL, pick events, done.

Set up the Slack side

1. In Slack, go to Apps → Custom Integrations → Incoming Webhooks (or your team's equivalent).
2. Pick the channel that should receive bichito reports. #bug-reports, #oncall, or your team channel works fine.
3. Copy the webhook URL — looks like https://hooks.slack.com/services/T…/B…/….

Set up the bichito side

1. In /{hive}/honeycombs/{id}/integrations, click New webhook.
2. Paste the Slack URL.
3. Pick events — most teams want just bug.created in Slack so the channel doesn't get noisy on every status change. You can opt into bug.commented and bug.updated if you want a fuller activity stream.
4. Set Transform to slack.
5. Save.

The first delivery fires the next time a matching event happens. Click Test webhook in the dashboard to verify with a synthetic payload.

What lands in Slack

For bug.created, the message looks like:

🐝 New bichito in Acme web Login button broken on Safari — high Steps: click the button, nothing happens. Open in dashboard ↗

Severity colours the side bar (high → orange, critical → red, low/medium → grey). The "Open in dashboard" link deep-jumps into the bichito.

For bug.commented:

💬 Comment on Login button broken on Safari "Looks like an old framework version — checking." [Open in dashboard ↗]

For bug.updated, only changes worth surfacing fire (status, severity, assignee). Label changes and duplicate-of are skipped from the Slack transform — they tend to be noisy.

Filtering further

If bug.created is still too noisy, common patterns:

• Per-severity routing. Register two Slack webhooks: one to #oncall for severity == "critical" || "high", one to #bug-reports for the rest. The dashboard doesn't expose severity filters on webhooks today — if you need this, get in touch and we'll prioritise.
• Only your honeycombs. Webhooks are per-honeycomb, so a multi-product hive can route each project to its own channel.

Removing the integration

Click Revoke on the webhook row. The Slack URL stays valid (it's owned by Slack) — you'd need to revoke it in Slack to fully kill the channel.