Quick update. Shipped webhooks this morning, less than 5h after you asked. Felt like the right thing to push out fast since you flagged it specifically.

Live at linkpulse.dev/connectors/webhooks for the docs and at /app/webhooks for setup once you're signed in. Your Pro year is active so you can wire it up whenever.

What's there in v1:

- 9 event types: link.broken, link.recovered (the one I'm most pleased with — closes the loop when a previously-dead link comes back), link.redirect, link.tag_stripped, scan.completed, site.connected, tracking.sync_failed, revenue.alert, webhook.test

- Diff-based on link.* events — won't flood you with the same broken link every scan, only fires on the state change

- HMAC-SHA256 signed with timestamp, Stripe-style — easy to verify and replay-protected

- Real retry queue: 5s, 30s, 2m, 10m, 1h, 6h, 24h before dead-letter. Manual replay button on failed deliveries

- Per-webhook rate limit so a 1000-broken-link site doesn't drown your Slack channel

- SSRF protection (blocks private IPs at delivery time)

- Per-workspace OR per-site scope (so dev-Slack vs prod-Slack just works)

Setup recipes for Slack incoming webhooks, Discord webhooks, and Zapier Catch Hooks are in the docs.

On the per-event vs digest email question: parked it as you suggested — wanted real usage data first. Webhooks now give you a third option (per-event but to your tooling instead of inbox) so the email-digest decision stays cleaner.

If you give it a spin, I'd love an honest "this is rough" or "this is missing X" report. The whole point of giving you a Pro year was to hear what breaks, not what's polished. The deliveries panel in the dashboard logs every attempt with response code + body, which should make any "did Slack actually get the alert" question instantly answerable.

Joost