Notifier overview
Learn how a Notifier routes selected Incident and Recovery Notification Events to a receiver, becomes ready for production, and reports Delivery Health.
Notifier is the PointWarden interface name for a Workspace-owned Notification Destination. It connects selected Incident and Recovery Notification Events to one public HTTPS receiver configured as Generic, Slack, Discord, or Microsoft Teams.
Subscriptions, verification, and lifecycle determine eligibility, while Delivery Health describes production delivery results.
How a Notifier routes an event
A Notifier begins downstream of monitoring. It routes a confirmed event to an eligible receiver and records what happened during delivery.
Create a Notification Event
Incident Confirmation or confirmed Recovery creates an immutable Notification Event for the Monitor.
Match eligible Notifiers
PointWarden matches the event type and Monitor subscription, then snapshots Notifiers that are Verified and Enabled at that moment.
Create a Delivery
One Delivery carries one Notification Event to one Notifier. The Delivery keeps the same identity across retries.
Record Delivery Attempts
Each request to the receiver becomes a Delivery Attempt. Production activity determines Delivery Health and retains safe outcome evidence.
Prepare a Notifier for delivery
Verification and lifecycle are separate state changes. A successful Test Delivery proves the saved receiver accepted the request, but it does not enable production delivery.
- After savingUnverified and Paused
- After a successful Test DeliveryVerified and Paused
- After enablingVerified and Enabled
Read a Notifier
Check these questions independently. A Verified Notifier can still be Paused, disconnected from events or Monitors, or show Failing Delivery Health.
| Question | Product state or evidence |
|---|---|
| Which events and Monitors are connected? | Connections and subscriptions. New Notifiers default to no events and no Monitors. |
| Has the saved receiver accepted a test? | Verification: Unverified or Verified. A successful saved Test Delivery verifies the Notifier. |
| Can it receive new matching events? | Lifecycle: Paused or Enabled. Only a Verified Notifier can be Enabled. |
| What happened in the latest production delivery? | Delivery Health: No Delivery Data, Delivering, Healthy, Retrying, or Failing. |
Choose the next task
Follow the Owner quickstart for the shortest complete setup. For the full Notification path, start with Configure a Notifier, then verify and enable it before you inspect Delivery evidence.
Use the provider target guides for Slack, Discord, or Microsoft Teams. If a receiver Delivery is missing, open Notifier and Delivery troubleshooting.