Notifications
Get alerts where your team already works. Blecon Track can notify you the moment a rule triggers — by email, webhook, or the in-app notification bell — so the right people know immediately without watching a screen.
Notification channels
Track supports two types of notification channel. You can use both at the same time, and each alert rule can send to any combination of channels.
Email channels
Email channels send formatted alert emails directly to your team's inboxes. Each channel holds a list of up to 10 recipient addresses.
Setting up email notifications:
- In Blecon Track, go to Settings > Email Channels.
- Click Add Email Channel and enter a name and recipient addresses.
- When creating or editing an alert rule, select which email channels should receive notifications.
Emails include the rule name, severity, device or zone involved, and a link to the violation in Blecon Track.
Webhook channels
Webhook channels send an HTTP POST to a URL you provide — Slack, PagerDuty, your own dashboards, or any system that accepts HTTP callbacks.
Setting up webhooks:
- In Blecon Track, go to Settings > Webhooks.
- Click Add Webhook and enter your endpoint URL.
- When creating or editing an alert rule, select which webhook channels should receive notifications.
When notifications are sent
Notifications are sent at three points in the violation lifecycle:
| Notification type | When it fires |
|---|---|
new |
A violation is created (rule condition detected) |
resolved |
A violation resolves automatically (condition cleared) |
status_changed |
An operator acknowledges or manually resolves a violation |
This means your external systems can track the full lifecycle — from detection through triage to resolution.
In-app notification bell
A bell icon in the navigation bar shows a red dot when there are active (unresolved) violations. Click the bell to go to the Alerts page where you can triage, acknowledge, and resolve violations.
Webhook payload
Each webhook notification is delivered as a JSON array containing a CloudEvents object. The payload includes:
- Alert rule — The rule name, type, and severity.
- Device or location — The device ID (or zone ID for zone asset count rules).
- Notification type —
"new","resolved", or"status_changed". - Violation status — Current violation state (
active,acknowledged, orresolved). - Timestamp — When the event occurred.
For status_changed notifications, the payload also includes:
- changed_by — Who acknowledged or resolved the violation.
- assignee — The assignee, if one was set during acknowledgement.
Signature verification
Each webhook POST includes an X-Tracker-Signature header containing an HMAC-SHA256 signature of the request body. Use this to verify that notifications came from Blecon and were not tampered with.
The header format is:
X-Tracker-Signature: sha256=<hex_digest>
Track notifications vs Network webhooks
Track notifications deliver alert events — rule triggers and violation lifecycle updates.
Blecon Network webhooks deliver raw data events — position updates, device connections, and sensor readings.
They serve different purposes and are configured in different places.