Event delivery

Get alerts and notifications where your team already works. Blecon Track can deliver an event the moment a rule fires — by email, Slack, Zapier, 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

Blecon Track supports four types of channel, and you can use any combination at once. They are listed in the order most teams adopt them: email needs nothing but an address, Slack puts alerts where your team already is, Zapier routes them onward to thousands of other apps, and webhooks carry events into your own systems.

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 Integrations and open the Event delivery tab.
Click + Add Email 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.

Slack channels

Slack channels post alerts into a Slack channel, colour-coded by severity, with the asset, rule and time as separate fields and a button back to the alert. Times are shown in each reader's own timezone.

A Slack channel needs an Incoming Webhook URL, which you get by creating a Slack app in your own Slack workspace. The app is private to that workspace: it is not published, not reviewed, and not visible to anyone else. Because you create and name it, alerts arrive under your own name and icon.

Setting up Slack delivery:

In Slack, go to api.slack.com/apps and choose Create New App, then From scratch. Name it whatever you want the alerts to appear as, and pick your Slack workspace.
Open Incoming Webhooks and turn it on.
Click Add New Webhook to Workspace, choose the channel, and click Allow. Copy the URL.
In Blecon Track, go to Integrations, open the Event delivery tab, and click + Add Slack. Paste the URL and name the channel after the Slack channel it posts to.
Click Test to post a sample alert, then select the channel on any rule.

Some Slack workspaces require an admin to approve new apps. If step 3 is blocked, ask a Slack admin to approve the app or to create the webhook for you.

Each webhook URL posts to exactly one Slack channel, permanently. To alert a second Slack channel, create a second webhook and add it here as another channel. Name each one after the Slack channel it targets: the URL does not say which, and Blecon Track has no way to look it up.

For security the URL is never shown again after you save it, because anyone holding it can post to that Slack channel. If it is ever revoked, create a new webhook and edit the channel to use it.

Zapier channels

A Zapier channel sends alerts to a Zap, which can then do almost anything: post to Microsoft Teams, append a row to Google Sheets, open a Jira ticket, send an SMS. One alert arrives as one Zap run.

Setting up Zapier delivery:

In Zapier, create a Zap with Webhooks by Zapier as the trigger and Catch Hook as the event. Copy the webhook URL.
In Blecon Track, go to Integrations, open the Event delivery tab, and click + Add Zapier. Paste the URL and name the channel.
Click Test. That sends a real alert, which is what gives Zapier sample data to map fields from.
Finish the Zap in Zapier, turn it on, then select the channel on any rule.

Zapier receives the same CloudEvents payload as a webhook channel, so the webhook payload reference describes every field available to a Zap. Filter on the event type if a Zap should only run for new alerts rather than resolutions too.

As with Slack, the URL is never shown again after you save it: anyone holding it can fire your Zap.

Full walkthrough: Send alerts to Zapier.

Webhook channels

Webhook channels send an HTTP POST to a URL you provide: PagerDuty, your own dashboards, or any system that accepts HTTP callbacks. Events arrive as CloudEvents JSON with an HMAC signature you can verify.

Setting up webhooks:

In Blecon Track, go to Integrations and open the Event delivery tab.
Click + Add Webhook and enter your endpoint URL.
When creating or editing a rule, select which webhook channels should receive its events.

A Slack Incoming Webhook URL will not work here, and is rejected: Slack requires its own message format and refuses the CloudEvents payload. Use a Slack channel instead.

Every event that can be delivered

There are five, and the event type tells you which without inspecting anything else.

Event type	When it fires	Email	Slack	Zapier / Webhook
`alert.triggered`	An alert rule's condition is detected	Yes	Yes	Yes
`alert.resolved`	The condition clears on its own	Yes	Yes	Yes
`alert.status_changed`	Someone acknowledges or manually resolves it	Yes	Yes	Yes
`notification.triggered`	A notification rule fires	Yes	Yes	Yes
`report.ready`	A scheduled report has finished generating	No	No	Yes

Alert rules (severity low, medium, high, or critical) deliver across the alert lifecycle, so all three alert.* types apply. The lifecycle_event field carries the same distinction as the type: new, resolved, or status_changed.

Notification rules (severity notification) deliver a single notification.triggered each time the rule fires. There is no lifecycle, so no resolution or status change follows, and no lifecycle_event field is sent.

report.ready has no email or Slack form, so a workspace that wants to be told when a scheduled report is ready needs a Zapier or webhook channel.

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 CloudEvents type is one of the five above, and the X-Webhook-Event header carries exactly the same value, so you can route on either. source is workspace/{workspace_id}. The payload includes:

Rule: The rule name, type, and severity.
Tag or location: The tag ID (or zone ID for zone asset count rules).
Lifecycle (lifecycle_event): "new", "resolved", or "status_changed". Sent on alert.* events only.
Timestamps: triggered_at is always when the alert originally fired; resolved events also include resolved_at.

For status_changed events, the payload also includes:

alert_status: The new state (acknowledged or resolved).
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-Webhook-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-Webhook-Signature: sha256=<hex_digest>