Event delivery

Get alerts and notifications where your team already works. Blecon Track can deliver an event the moment a rule fires — by email, webhook, or the in-app bell — so the right people know immediately without watching a screen.

Event delivery carries both kinds of rule output:

Alerts — actionable conditions that persist until resolved.
Notifications — informational, fire-and-forget events.

You configure delivery channels once, and each rule can send to any combination of them.

Delivery channels

Track supports two types of channel. You can use both at the same time.

Email channels

Email channels send formatted emails directly to your team's inboxes. Each channel holds a list of up to 10 recipient addresses.

Setting up email delivery:

In Blecon Track, go to Event delivery > Email channels.
Click Add email channel and enter a name and recipient addresses.
When creating or editing a rule, select which email channels should receive its events.

Emails include the rule name, severity, the tag or zone involved, and a link to the event 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 Event delivery > Webhooks.
Click Add webhook and enter your endpoint URL.
When creating or editing a rule, select which webhook channels should receive its events.

When events are delivered

What gets delivered depends on whether the rule raises an alert or sends a notification.

Alert rules (severity low, medium, high, or critical) deliver across the alert lifecycle:

Event type	When it fires
`new`	An alert is created (rule condition detected)
`resolved`	An alert resolves automatically (condition cleared)
`status_changed`	An operator acknowledges or manually resolves an alert

Notification rules (severity notification) deliver a single new event each time the rule fires. There is no lifecycle, so no resolved or status_changed events are sent.

In-app notification bell

A bell icon in the navigation bar shows a dot when there are active or acknowledged alerts that need attention. Click the bell to go to the Alerts page to triage, acknowledge, and resolve them.

The bell tracks alerts only — notification-only events do not light it, because there is nothing to action. Find those on the Notifications page.

Webhook payload

Each webhook is delivered as a JSON array containing a CloudEvents object. The payload includes:

Rule: The rule name, type, and severity.
Tag or location: The tag ID (or zone ID for zone asset count rules).
Event type: "new", "resolved", or "status_changed".
Status: For alerts, the current state (active, acknowledged, or resolved).
Timestamp: When the event occurred.

For status_changed events, the payload also includes:

changed_by: Who acknowledged or resolved the alert.
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 the request came from Blecon and was not tampered with.

The header format is:

X-Tracker-Signature: sha256=<hex_digest>

Track event delivery vs Network webhooks

Track event delivery carries rule output: alert lifecycle updates and notifications.

Blecon Network webhooks deliver raw data events: position updates, tag connections, and sensor readings.

They serve different purposes and are configured in different places.