Notification channels
NiteWtch separates personal wake-up contact (voice and SMS) from tenant integrations (outbound webhook, outbound Slack webhook, and email fanout). Voice escalation follows on-call groups; integrations fire on alert events you filter per channel. Customer-facing inbound webhook ingest is not available yet.
Setup order
- Set your phone on Profile and verify voice/SMS delivery with the test buttons.
- Tenant admins enable SMS on On-Call Groups when the tenant should send texts.
- Configure outbound webhook, outbound Slack webhook, and/or email on Notification Channels — each channel has its own filters.
- Use Test on each enabled card before relying on it in production.
- Review Delivery Status at the bottom of Notification Channels for success, failure, and skip reasons.
Guides
- Outbound webhook — POST signed JSON alert payloads to your HTTPS endpoint. NiteWtch signs the body with your shared secret in the X-Nite-Signature header.
- Outbound Slack webhook — NiteWtch POSTs alert notifications to your hooks.slack.com URL (Slack calls this an Incoming Webhook in their UI).
- Email fanout — Send alert notification emails to a comma-separated recipient list. Delivery uses Mailgun HTTPS with SMTP fallback.
- Voice & SMS (personal contact) — Voice wake-up calls and SMS alerts go to on-call users — not through the Notification Channels integration cards. Configure your number on Profile; admins control tenant SMS on On-Call Groups.
- Daily & weekly digest — Scheduled operational email summaries — separate from real-time alert fanout. Configure recipients, timezone, and send window on Digest Reports.
In-app copy is sourced from the same content module as these pages.