Notification channels
Nexus supports two notification channels, which you can use independently or together:Nexus sends notifications directly to individual users or distribution lists. No additional integration setup is required — just enter the recipient addresses and toggle on the events you care about.
Webhooks
Nexus POSTs a JSON payload to any URL you specify. Use webhooks to route alerts to Slack, Microsoft Teams, PagerDuty, or any custom endpoint in your environment.
Email notifications
Email notifications keep individuals and distribution lists informed without requiring them to log in to Nexus. The following notification types are available:
To configure email notifications:
1
Open the Email notifications page
Go to Settings > Notifications > Email.
2
Enable the event types you need
Toggle on each event type you want to receive notifications for.
3
Add recipient addresses
Enter one or more email addresses in the field below each event type. You can use individual addresses or a distribution list address.
4
Save your changes
Click Save to apply your configuration.
Webhook notifications
Webhooks let you push Nexus events into any system that can receive an HTTP POST request. This is the recommended approach for real-time alerting in tools like Slack or Microsoft Teams.1
Open the Webhooks settings page
Go to Settings > Notifications > Webhooks and click New Webhook.
2
Enter the destination URL
Paste the full URL of the endpoint that should receive the webhook payloads. For Slack, this is your Incoming Webhook URL. For Microsoft Teams, use your Teams channel’s workflow webhook URL. For custom endpoints, make sure the URL is publicly reachable over HTTPS.
3
Select trigger events
Choose which event types should trigger this webhook. You can select one event type or multiple — the same event types available for email notifications apply here. A single webhook URL can listen for as many event types as you need.
4
Add a signing secret (optional)
If your receiving endpoint supports payload verification, enter a secret string in the Signing Secret field. Nexus will sign every payload using HMAC-SHA256 and include the signature in the
X-Nexus-Signature request header. Your endpoint can use this to confirm the payload genuinely came from Nexus and hasn’t been tampered with.5
Save and verify the connection
Click Save. Nexus immediately sends a test ping to the destination URL to verify it’s reachable. If the ping succeeds, the webhook status shows Active. If it fails, check that the URL is correct, publicly accessible, and returns a
2xx HTTP response.Webhook payload format
Every webhook event Nexus sends follows the same JSON envelope structure. Theevent field identifies the type of event, and the remaining fields provide context specific to that event type. Below is an example payload for a new high-severity finding:
tenant_id field contains the primary domain of the Entra tenant where the event originated, which is useful when you have multiple tenants connected to Nexus and want to route alerts to tenant-specific channels. Refer to the Nexus Settings documentation for additional configuration options.