IT OPS
Page After-Hours Building Anomalies to the Duty Manager in Teams
Filters incoming sensor anomalies by time of day, and during nights and weekends routes only safety-critical faults (fire, water, power.
How it runs
The automated pipeline, trigger to output.
- TriggerAnomaly received via webhookHTTP webhook
- LogicCheck after-hours window and safety-critical fault type
- ActionQueue non-urgent events in Airtable for next dayAirtable
- ActionOpen PagerDuty incident for duty managerPagerDuty
- OutputDirect-message duty manager in Microsoft TeamsMicrosoft Teams
What it does
After hours there is no full ops desk, so this workflow applies a stricter filter: only the faults that genuinely cannot wait until morning reach the duty manager, and everything else is queued for the next business day.
When to use it
Use it for buildings that are unstaffed overnight and on weekends, where you want to protect the duty manager from non-urgent noise but guarantee that a flooding sensor or a freezer over-temp gets immediate attention.
How it works
- 1An HTTP webhook receives the anomaly event with type, reading, and timestamp.
- 2A logic step checks whether the event falls inside after-hours coverage and whether the fault type is on the safety-critical list.
- 3Non-critical or in-hours events are logged to Airtable as queued for the next business day and the flow ends.
- 4Safety-critical after-hours faults open a PagerDuty incident for the duty manager.
- 5The output sends a direct Microsoft Teams message to the duty manager with the location and recommended first action.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect AirtableBases, tables, views, automations.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 4Connect Microsoft TeamsChannels, chats, files.
- 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
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.
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.
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.
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.
Monthly Wasted-License Cost Report
Aggregates inactive-seat data across all tracked SaaS apps each month, computes total reclaimable spend, and delivers a ranked cost report to leadership in Notion and Slack.
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.