Slack webhooks
Test and debug Slack webhooksfrom Block Kit to Events API
Capture the messages your app posts and the events Slack sends back. Read the exact JSON, check request signatures and fix formatting before a channel sees it.
How Slack webhooks work
| Where to configure it | App settings > Event Subscriptions: turn it on and choose an HTTP request URL (or Socket Mode), then subscribe to event types. |
|---|---|
| Signature header | X-Slack-Signature: v0= followed by the HMAC-SHA256 of "v0:" + X-Slack-Request-Timestamp + ":" + raw body, keyed with your signing secret. |
| Replay window | Slack's verification guide ignores requests whose X-Slack-Request-Timestamp is more than five minutes from local time, as a guard against replay attacks. |
| Timeout | Respond with HTTP 2xx within three seconds or the delivery counts as failed. |
| Retries | Up to 3 retries: nearly immediately, after 1 minute, then after 5 minutes, with x-slack-retry-num (1-3) and x-slack-retry-reason headers. |
Sources (checked November 2026)
Ship Slack automations your team trusts
Slack webhooks drive deal alerts, on-call escalations and launch announcements. Hooklistener captures every payload as it arrives so you can debug formatting, rate limits and retries before someone misses a critical ping.
Replace curl scripts with a request history you can search. Share a debugger link with the person who owns the channel instead of pasting JSON into a thread.
Where Slack teams get stuck
Broken Block Kit
One misplaced comma breaks a whole Block Kit message. You need the exact JSON your app sent, not the error Slack returned.
Mystery rate limits
Slack's HTTP 429s do not tell you which payload failed. Without a history of what you sent, the message is simply gone.
Siloed operations
Engineering owns the webhook, but sales and support own the channel. Everyone needs to look at the same request to agree on what went wrong.
How Hooklistener helps with Slack webhooks
Slack signature verification
Store your Slack signing secret (paid plans) and check the X-Slack-Signature on each captured Events API request, so a failing signature check shows whether the secret or your code is wrong.
Inspect the Block Kit JSON
Send a Slack message to a Hooklistener endpoint first and read the exact blocks and attachments your app produced before a malformed payload reaches a production channel.
Shareable debugger links
When a Slack alert never shows up, send the channel owner a link to the captured request so sales, support and engineering all look at the same payload.
Try it: point Slack at a free webhook URL or run a test with the webhook tester.
Slack webhooks worth instrumenting
Sales pipeline alerts
Push CRM updates into dedicated channels and confirm every payload renders before reps rely on it.
Incident management
Stream PagerDuty or monitoring signals into war rooms and keep the captured payloads for the post-mortem.
Release announcements
Automate product announcements and release notes without hand-checking message formatting every sprint.
Replay a failed webhook without re-triggering the provider
Once a delivery is captured, you can resend its exact headers and body to localhost, staging or production from the dashboard or through your coding agent over MCP, so the provider never has to fire a new event. Replay is on Pro and above. Read the replay guide.
Comparing webhook debugging tools?
See how Hooklistener stacks up against webhook.site, RequestBin, Beeceptor, Hookdeck and ngrok in the best tools to capture and inspect webhook payloads, or read the head-to-head pages for Hooklistener vs ngrok and Hooklistener vs Beeceptor.
Frequently asked questions
Can Hooklistener preview Slack message formatting?
It shows the JSON. Capture the payload and check the Block Kit blocks, attachments and text fields before you post to a live channel. Use Slack's Block Kit Builder to see how the message renders.
How do I debug Slack rate limits?
Send your messages through a Hooklistener endpoint while testing and every request stays in the history for your plan's retention, so you can see which payload was in flight when Slack returned 429. Replay is on Pro and above.
Can Hooklistener verify Slack request signatures?
Yes. Signature verification covers Stripe, GitHub and Slack. Store your Slack signing secret (paid plans) and Hooklistener checks the X-Slack-Signature header on captured requests.
Can I test Slack Workflow Builder webhooks?
Yes. Point a Workflow Builder webhook step at a Hooklistener endpoint to capture the JSON it sends, then point it at your own service once the fields look right.
Keep every Slack webhook on tempo
Capture, inspect and verify Slack webhooks in minutes, and give RevOps, support and engineering the same view of each request.