nano SIEM
Settings

Notifications

Supported in:Self-hosted

Deliver alerts, case activity, and scheduled reports to Slack, Microsoft Teams, PagerDuty, or any webhook endpoint via notification channels.

Configure notification channels to send alerts and platform events to your external systems. Each channel combines a destination with routing rules; nano delivers an event to every channel whose filters match.

Manage channels at Settings → Notifications (/settings/notifications). The old Settings → Webhooks page redirects here.

Channel types

TypeDelivery mechanism
SlackIncoming Webhook — posts a message card to one Slack channel
Microsoft TeamsAdaptive Card posted to an incoming-webhook / workflow URL
PagerDutyEvents API v2, configured with a routing key; the alert id is used as the dedup key
Generic webhookHMAC-SHA256-signed JSON POST to any URL, with optional custom headers

Email channels aren't available yet: creating one is refused until email delivery ships.

Setting up a Slack channel

Open your Slack app

Go to api.slack.com/apps and select your app (or create one).

Activate Incoming Webhooks

Under Features → Incoming Webhooks, toggle Activate Incoming Webhooks on.

Add a webhook for the destination channel

Click Add New Webhook to Workspace and pick the Slack channel that should receive notifications. Slack generates a https://hooks.slack.com/services/… URL — copy it.

Create the channel in nano

On Settings → Notifications, create a new Slack channel and paste the webhook URL as the channel's URL. Configure its routing rules, then use Test send to confirm delivery.

Microsoft Teams

Teams notifications are delivered as an Adaptive Card posted to an incoming-webhook / workflow URL. Create the workflow in Teams, copy its URL, and paste it as the channel's URL in nano.

PagerDuty

PagerDuty channels use the Events API v2. Configure the channel with the routing key (integration key) of the PagerDuty service that should receive events. The alert id is used as the dedup key, so repeated deliveries for the same alert de-duplicate on the PagerDuty side rather than opening new incidents.

Generic webhook

A generic channel sends an HMAC-SHA256-signed JSON POST to the URL you configure, so the receiver can verify the payload came from your nano instance. Custom headers are supported — useful for API keys or routing hints your endpoint expects.

Existing webhooks from the old Webhooks page continue to work as generic channels.

Routing rules

Each channel subscribes to one or more event types:

Event typeFires on
SIEM alertsDetection-rule alerts
Observability alertsAlerts from observability (traces / metrics) rules
CasesCase activity
Scheduled reportsCompleted scheduled report runs
System healthPlatform health issues (integrations, enrichment, log sources, ingest, parsers and more)

New channels subscribe to SIEM alerts and Observability alerts by default.

On top of the event types, each channel sets:

  • Minimum severity — events below it are not delivered to this channel.
  • Detection-rule filter (optional) — restrict the channel to specific rules.
  • Health category and resource filters (optional, for System health) — restrict health notifications to some categories or named resources.

An event is delivered to every channel whose subscriptions and filters match — routing is fan-out, not first-match.

Testing and delivery history

Every channel has:

  • Test send — dispatches a sample notification through the real delivery path so you can verify the destination end-to-end.
  • Recent delivery log — the channel's latest delivery attempts and their outcomes, for troubleshooting failed or missing notifications.

Reliability and security

The delivery spine validates egress destinations against SSRF (a channel can't be pointed at internal infrastructure), retries failed deliveries with backoff, and stores channel secrets (webhook URLs, routing keys, HMAC secrets) encrypted at rest.

Permissions

PermissionGrants
settings:webhooksManage notification channels and their routing rules

Troubleshoot

Need help with these checks? Contact support with the request ID and time with timezone.

Set the base URL on the Notifications page to the external URL analysts use. Without it, cards are delivered without a clickable link.

An expected alert is missing

Check the event subscription, minimum severity, and detection-rule filter. Review the recent delivery log and use Test send to check the destination.

What's next

On this page