IT OPS
Route HVAC sensor anomalies to the right vendor on-call
Receives HVAC sensor alerts via webhook, classifies severity by deviation from setpoint, and pages the assigned mechanical vendor's on-call while logging the incident to Airtable.
How it runs
The automated pipeline, trigger to output.
- TriggerHVAC sensor posts reading to webhookHTTP webhook
- LogicCompute deviation and classify severity
- ActionPage mechanical vendor on-call (critical)PagerDuty
- ActionPost advisory to facilities channelSlack
- OutputLog incident to maintenance trackerAirtable
What it does
Turns raw HVAC sensor alerts into a triaged incident routed to the correct vendor. It reads the building, zone, and temperature deviation from the incoming payload, decides whether the anomaly is critical or advisory, and either pages the mechanical vendor's on-call rotation or files a low-priority work item. Every alert is logged to a maintenance tracker for audit and SLA reporting.
When to use it
Use this when building management sensors (BMS, Honeywell, smart thermostats) post temperature, humidity, or pressure readings to a webhook and you want anomalies routed automatically to the vendor responsible for that system instead of a shared inbox someone has to watch.
How it works
- 1A sensor reading arrives at the webhook with building, zone, metric, value, and setpoint.
- 2A logic step computes deviation from setpoint and classifies severity (critical if outside the safe band, else advisory).
- 3Critical anomalies page the mechanical vendor's PagerDuty on-call with zone and reading context.
- 4Advisory anomalies post to the facilities Slack channel for next-business-day follow-up.
- 5The incident is appended to an Airtable maintenance log with severity, vendor, and timestamp.
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.
- 4Connect AirtableBases, tables, views, automations.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More IT Ops workflows
Recurring Sensor Fault Root-Cause Investigator
On a schedule, an agent reviews recent Monday work orders and BigQuery telemetry to identify equipment with repeating faults, drafts a root-cause hypothesis with a recommended fix.
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.
Agentic Inactive-Seat Reclamation Review
An agent investigates each idle SaaS seat by correlating SSO login gaps with HR status and ticket history, classifies it as reclaim, hold, or escalate, and drafts a reasoned…
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.
Approved-Seat Deprovision Execution
Fires when an IT approver confirms a seat for removal, then executes deprovisioning via the IdP API and logs the action to an audit table and a Linear cleanup ticket.
HVAC Anomaly Detection to Severity-Routed Work Orders
Ingests building HVAC telemetry via webhook, flags out-of-band temperature, pressure, or runtime readings.
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.