Alerts
Alerts overview
Know immediately when listings, scores, or Google reputation change: routed to the right people through the channels you already use.
The alert pipeline
SenderSignal alerts follow a simple pipeline:
- Event: something changed (listed, delisted, score drop, Postmaster reputation shift)
- Alert record: created in your workspace with severity, asset, and detail
- Rules: optional filters (which event types matter for this route)
- Channels: email, Slack, webhook endpoints subscribed to event types
- Delivery: notifications sent; delivery log shows success or retry errors
Where to configure
Open Alerts in the sidebar. You will find:
- Settings: global toggles and thresholds (Postmaster, score deltas, etc.)
- Channels: connect email recipients, Slack, webhooks
- Rules: fine-grained routing (optional)
- Feed: live alert stream and acknowledgement
Common event types
| Category | Examples |
|---|---|
| Blacklist | listed, delisted |
| Score | score_drop, score_rise |
| Deliverability | Auth record changes, SMTP failures (plan-dependent) |
| Postmaster | Reputation change, compliance change, spam rate threshold |
Rules vs channels
Channels are destinations (email addresses, Slack workspace, HTTPS URL). Each channel subscribes to one or more event types.
Rules add optional logic: e.g. only send listed for production domains, or route critical events to a PagerDuty webhook. If no rule matches, channel subscriptions still deliver matching events.
Detailed guide: Rules & routing.
Permissions
Viewing alerts requires Alerts module access. Creating channels and editing rules typically requires alerts.channels.manage and alerts.rules.manage respectively (or admin roles).