Use case · Scaling a Team
When your team outgrows email alerts.
Solo devs run on email. Growing teams run on Slack and Discord. The moment a second person needs to see a webhook in real time, the inbox-and-screenshare workflow breaks — and that's exactly the gap Scale fills.
What's painful today
- Webhook failures land in one developer's inbox; the rest of the team finds out hours later — at standup, or when a customer complains.
- Three people sharing the same Hook-plan login means audit logs lie about who replayed what, and seat limits cap real collaboration at the wrong size.
- Stripe lives in one channel, GitHub in another, Shopify in a third — but no tool mirrors the captured event into the channel where the team already is.
How HookSense solves it
Slack / Discord mirroring of every capture
Forward every captured webhook into a Slack or Discord channel — method, status, provider, HMAC badge, and a link back to the inspector. Your team sees the live stream where they already work, not in a separate dashboard.
5 team seats, real role separation
Scale jumps Hook's 3-seat cap to 5 — enough for a backend team plus a QA partner and an SRE-on-call. Owner / admin / member / viewer roles map to who can edit, who can replay, and who can only look.
30 endpoints + 60-day retention
Doubles Hook's 15-endpoint cap, doubles its retention. Teams running 8+ provider integrations (Stripe + Stripe Connect + GitHub + Shopify + Slack + Twilio + SendGrid + custom) finally fit, and incident post-mortems can look back two months.
See it in code
Wire a Slack channel to receive every captured webhook
# 1. In Slack: Apps → Incoming Webhooks → Add to Slack → pick channel
# 2. Copy the webhook URL (https://hooks.slack.com/services/...)
# 3. In HookSense: endpoint → Forwards panel → Add forward
# Or via API:
curl -X POST https://hooksense.com/api/endpoints/<slug>/forwards \
-H "Authorization: Bearer hsk_..." \
-H "Content-Type: application/json" \
-d '{
"type": "slack",
"targetUrl": "https://hooks.slack.com/services/T.../B.../...",
"includeBody": true
}'
# Every webhook captured at /w/<slug> now also posts to your Slack channel.
# Max 10 forwards per endpoint. Fire-and-forget — never blocks capture.FAQ
How is Forwarding different from Alerts?
Forwarding mirrors every webhook into a channel — including the successful ones — so the team has live visibility into the stream. Alerts only fire when a rule trips (failure rate, inactivity, latency spike). Most teams run both: a #stripe-stream channel for the firehose, a #stripe-incidents channel for paging.
Why $29 Scale and not $49 Sense?
Sense adds production-grade features that small teams rarely need yet — custom domains, auto-retry with exponential backoff, AI-assisted failure diagnosis, IP allowlisting. Scale is the tier built for teams that have outgrown the solo workflow but aren't running mission-critical webhook infrastructure yet. When you do hit that point, the upgrade is one click.
Will Slack/Discord get spammed during a load test?
Each forward has an enabled toggle — mute it before a load test, re-enable when you're done. Body previews are also capped at 1,500 characters, so even chatty events don't blow up the channel.
What if our team already pages from PagerDuty / Opsgenie?
Use Alerts (with email or Slack to a PD-integrated channel) for incident routing, and Forwards for visibility into the normal stream. PagerDuty integrations sit downstream of Slack alerts in most setups — no need for HookSense to integrate with them directly.