Integrations

Slack Incident Reporting Guide

Configure a Slack incoming webhook connection in Logger and use it for manual sends, lifecycle automation, and scheduled digests.

Use a Slack incoming webhook, not a Slack workspace install

Use a Slack incoming webhook, not a Slack workspace install

Slack uses an outbound incoming-webhook connection. Workspace admins save the webhook URL once, optionally add a default channel label for operator context, and only see a masked preview after creation.

Choose manual send or server-side automation

Choose manual send or server-side automation

From the connection detail page, workspace admins can test Slack delivery and manually send a completed analysis. The same connection can also power `analysis_completed`, `analysis_failed`, `report_generated`, `daily_digest`, or `weekly_digest` automation rules.

Review delivery outcomes separately

Review delivery outcomes separately

Slack sends do not block the main analysis workflow. Logger records manual sends and automation deliveries in delivery logs so admins can confirm success, inspect failures, and iterate without losing the original investigation.

Why teams choose HendrixMojo

Evidence-first incident analysis for teams that need failure groups fast.