Alerts & Integrations

An alert you can't route is a dashboard you have to babysit.

SenderSignal turns ~60 event types, listings, DMARC changes, score drops, ramp milestones, into messages that reach the right place: email, Slack, or an HMAC-signed webhook into your own systems.

webhook · delivery · acme.io
Event coverage

~60 event types, six families.

Everything the platform observes can become an alert, and every channel subscribes to exactly the event types it cares about, nothing more.

Blacklists

Listings & delistings

Hear about a new listing the moment it's confirmed, and again when the delisting clears.

Reputation

Score drops & rises

Movements in the 0-100 reputation score, in both directions.

Deliverability

Config drift

MX change, certificate expiry, DMARC weakened, SPF invalid, the quiet changes that break mail.

Infrastructure

IP health

Signals on the sending IPs behind your mail, not just the domains in front of it.

Inbox Boost

Ramp lifecycle

Ramp started, paused by the bounce guard, resumed, completed, the moments worth knowing.

Account

Billing

Credit and subscription events, so finance surprises don't become deliverability surprises.

Channels

Live today, and what's rolling out.

We label channel status honestly, three are live now, three are on the way.

ChannelStatusNotes
EmailLiveIncluded on all plans
SlackLiveRich formatted messages · Professional plan and above
Signed webhooksLiveHMAC-SHA256 X-SenderSignal-Signature, custom headers, versioned JSON · Professional plan and above
PagerDutyRolling outEvents API v2
Microsoft TeamsRolling out 
DiscordRolling out 
Routing & reliability

Built by people who have been paged at 3am for nothing.

An alerting system earns trust two ways: staying quiet when nothing matters, and never going quiet when something does.

  • Per-channel subscriptions, each channel opts into specific event types
  • Rules & routing, send the right events to the right place
  • Cooldowns, a flapping condition can't become an alert storm
  • Test-send per channel, verify the pipe before you rely on it
  • Per-attempt delivery history, every attempt recorded, success or failure
  • Auto-pause on failure, a dead webhook can't silently eat alerts
channel · delivery history
Questions

Alerts & integrations, explained.

Which channels are live today?
Email, Slack (rich formatted messages) and generic webhooks signed with HMAC-SHA256. PagerDuty (Events API v2), Microsoft Teams and Discord are rolling out.
How are webhooks secured?
Every delivery is signed with HMAC-SHA256 and the signature travels in the X-SenderSignal-Signature header, so your endpoint can verify the payload really came from us. You can add custom headers, and the JSON payload is versioned so your handler doesn’t break when we add fields.
How do I stop alert storms?
Three layers: per-channel event-type subscriptions (each channel only hears about what it cares about), alert rules and routing to direct events to the right place, and cooldowns so a flapping condition can’t page you thirty times an hour.
What happens when a webhook endpoint dies?
Channels auto-pause after repeated delivery failures, so a dead webhook doesn’t silently eat alerts while you believe you’re covered. Every attempt is recorded in a full per-attempt delivery history, and there’s a test-send button per channel to verify things end to end.
Which plans get which channels?
Email alerts are on all plans. Slack and webhooks come with the Professional plan and above.
What kinds of events can fire?
Around 60 event types across blacklist listings and delistings, reputation score drops and rises, deliverability changes (MX change, certificate expiry, DMARC weakened, SPF invalid and more), IP health, Inbox Boost lifecycle, and billing.
Start free in two minutes

Stop checking the dashboard. Get told.

Email alerts on every plan, connect Slack or a signed webhook on Professional.