When your team outgrows email alerts.

What's painful today

• Callback 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 callback into the channel where the team already is.

How HookSense solves it

HookSense is the callback layer for AI agents: an agent calls create_callback_endpoint, awaits the result with wait_for_callback, and trusts it because verify_signature already checked it.

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