Skip to content

Send alerts to Zapier

Connect Blecon Track to Zapier and route alerts onward to anything Zapier reaches: Microsoft Teams, Google Sheets, Jira, ServiceNow, SMS, or your own internal tools. One integration, thousands of destinations.

Each alert arrives as one Zap run, so a Zap that logs a row, opens a ticket, or sends a message runs exactly once per alert.

What people build with it

  • Post alerts to Microsoft Teams. Microsoft retired Office 365 connectors in May 2026, so posting to Teams now needs a flow your organisation owns. A Zap is the least work.
  • Log every alert to Google Sheets or Airtable. A running record you can filter and chart, without anyone exporting anything.
  • Raise a ticket in Jira or ServiceNow. Turn "asset left the site" into work someone is assigned.
  • Text the duty manager via Twilio. For the rules where an email will not be read in time.
  • Escalate on-call through PagerDuty or Opsgenie. Route critical alerts into whoever is on rota.

Prerequisites

  • A Blecon Track workspace with at least one alert rule
  • A Zapier account

Step 1: Create the Zap trigger

  1. In Zapier, create a Zap.
  2. Choose Webhooks by Zapier as the trigger app.
  3. Choose the Catch Hook event and continue.
  4. Copy the custom webhook URL Zapier gives you.

Step 2: Add the Zapier channel in Blecon Track

  1. Go to Integrations and open the Event delivery tab.
  2. Click + Add Zapier.
  3. Paste the webhook URL, give the channel a name, and save.
  4. Click Test. This sends a real alert to your Zap, which is what gives Zapier sample data to build against.

For security the URL is never shown again after you save it: anyone holding it can fire your Zap with data of their choosing.

Step 3: Build the rest of the Zap

  1. Back in Zapier, the Catch Hook step now shows the test alert. Zapier lists its fields for you to map.
  2. Add whatever action you want, mapping fields from the alert.
  3. Turn the Zap on.

Step 4: Attach the channel to alert rules

  1. Open the rule you want to send to Zapier.
  2. Under Notifications, select your Zapier channel.
  3. Save.

What the alert looks like

Zapier receives the same payload as a webhook channel: a CloudEvents object carrying the rule name, type and severity, the asset involved, the event type (new, resolved, status_changed) and timestamps. The webhook payload reference lists every field.

The fields most Zaps use:

Field What it holds
data__rule_name The rule that fired, e.g. "Van left the depot"
data__severity notification, low, medium, high or critical
data__device_name The asset involved
type Which of the five event types this is
data__lifecycle_event new, resolved, or status_changed (alerts only)
data__triggered_at When the alert fired

Filter on the CloudEvents type if you only want new alerts: without it, a Zap that opens a ticket will also run when the alert resolves. The types are alert.triggered, alert.resolved, alert.status_changed, notification.triggered and report.ready.

Reaching Microsoft Teams this way

Teams is a good reason to use Zapier rather than a direct integration. Microsoft retired Office 365 connectors in May 2026, so posting to Teams now means a Power Automate or Zapier flow that your organisation owns. Adding a Teams action to a Zap gets you there without managing that flow yourself.

Questions? Contact Blecon support — we're happy to help.