Route Webhook Alerts Directly to Slack
Real-time webhook debugging for developers
Step-by-Step Setup
Get your HookCheck pipeline connected to #dev-alerts in under three minutes.
1. Generate a Slack Incoming Webhook
Open your workspace settings, navigate to Apps > Manage > Add an App, and search for "Incoming Webhooks". Enable it for the `#hookcheck-deployments` channel and copy the generated URL ending in `/T04X9K2P1/B07M3N8Q5/a8f2c1d`. Never share this URL publicly.
2. Configure the HookCheck Destination
In your HookCheck dashboard, go to Project Settings > Destinations. Select "Slack" from the dropdown, paste your webhook URL, and assign it to the `production-logs` and `staging-tests` pipelines. Enable JSON payload parsing to preserve stack traces.
3. Verify & Test the Connection
Click "Send Test Payload" in the destination modal. You should see a formatted card appear in Slack within 200ms, showing the `request_id`, `timestamp`, and `status_code`. Use the retry toggle if your workspace requires TLS 1.2 validation.
Why Route to Slack?
Eliminate context switching and keep your engineering team aligned on pipeline health.
Instant Visibility
Receive formatted alerts directly in `#ops-incidents` or `#backend-dev`. Webhook failures, timeout errors, and payload size warnings trigger threaded messages with direct links to the HookCheck replay panel.
Customizable Alert Thresholds
Define rules like "Notify only on HTTP 5xx" or "Suppress retries below 200ms". HookCheck filters 14,000+ daily test requests down to 12 actionable Slack notifications per engineer.
Zero-Configuration Retries
If Slack's API returns a 429 rate limit or your workspace experiences a brief outage, HookCheck automatically queues payloads for exponential backoff delivery without dropping critical debugging data.