IT OPS

Critical Sensor Anomaly to PagerDuty On-Call

Receives sensor breach webhooks, and when a critical asset (server-room cooling, water leak.

CategoryIT Ops
Enginesim
Difficultybeginner
Triggerwebhook
Steps4
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSensor breach webhook from BMS/IoT gatewayHTTP webhook
  • LogicCheck if asset is on critical list
  • ActionPage facilities on-call via PagerDutyPagerDutyPagerDuty
  • OutputLog every breach to facilities Slack channelSlack

What it does

Separates urgent facilities incidents from routine noise. Critical-asset anomalies wake someone up through PagerDuty; everything else is logged quietly so the on-call engineer is only paged when a person actually needs to respond tonight.

When to use it

Use this when you have a small set of high-stakes assets (server-room HVAC, leak detectors, fire/life-safety panels) where a breach demands immediate human response, and you want strict separation from low-priority alerts.

How it works

  1. 1An incoming HTTP webhook delivers a sensor breach payload from your IoT gateway or BMS.
  2. 2A branch checks whether the asset ID belongs to the critical-asset list.
  3. 3For critical assets, an action triggers a PagerDuty incident with the asset, reading, and threshold in the alert body.
  4. 4For non-critical assets, the flow skips paging.
  5. 5A final Slack message logs every breach (critical and routine) to the facilities monitoring channel for the record.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect PagerDutyIncidents, on-call, escalations.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.