IT OPS
Route IoT Sensor Anomalies to the Right Building Ops Channel by Severity
Receives sensor anomaly webhooks from your building management system, classifies each by severity and equipment type.
How it runs
The automated pipeline, trigger to output.
- TriggerBMS posts sensor anomaly to webhookHTTP webhook
- LogicScore severity by reading delta and equipment class
- ActionOpen PagerDuty incident for critical/high faultsPagerDuty
- ActionPost alert card to facilities Slack channelSlack
- OutputReturn routing decision to BMS for acknowledgementHTTP webhook
What it does
This workflow is the front door for every anomaly your building management system (BMS) detects. It ingests the raw alert, decides how urgent it is, and routes it so the right people see it within seconds — without flooding ops with noise.
When to use it
Run this when sensors (HVAC, water, power, air quality) emit anomaly events and you want one consistent triage path instead of alerts scattered across emails and dashboards. Ideal for facilities teams covering multiple buildings on rotating on-call.
How it works
- 1An HTTP webhook receives the anomaly payload from the BMS (sensor ID, reading, threshold, location).
- 2A logic step scores severity from the reading delta and equipment class (e.g. a chiller over temp = critical, a meeting-room CO2 blip = low).
- 3Critical and high anomalies branch to PagerDuty, opening an incident assigned to the on-call building engineer.
- 4Medium and low anomalies branch to Slack, posting a formatted card to the facilities channel.
- 5The final output writes the routing decision and timestamp back to the webhook caller so the BMS can mark the alert as acknowledged.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
Outlook Room Conflict Resolver with Approval Gate in Teams
When an Outlook room clashes, proposes a rebooking and asks the bumped meeting's organizer to approve the move in Microsoft Teams before any change is made.
Outlook Room Double-Booking Resolver with Auto-Rebook
Detects when two meetings claim the same Outlook room resource and automatically relocates the lower-priority meeting to a comparable free room.
Self-Service Reclaim Email for Idle Users
Detects users idle in a SaaS app past the threshold and emails each one a keep-or-release link; unanswered seats after the deadline are auto-flagged for removal.
Reconcile SSO logins against expense spend to find unmanaged tools
Joins SSO usage data with expense/payment records in Snowflake to surface tools that are being used but not paid for, or paid for but never logged.
Indoor Air Quality Breach to Tenant Notice and Work Order
Listens for CO2, VOC, or humidity sensor alerts via webhook, and when a zone exceeds occupant-safety limits it emails affected tenants, opens a Monday remediation task.
Daily Building Anomaly Digest to MS Teams
Each morning queries BigQuery for the prior day's flagged sensor anomalies, summarizes them by site and system into a ranked briefing.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.