IT OPS
Power Draw Spike Detection with PagerDuty Escalation
Polls Datadog for building electrical metrics, detects sustained power draw spikes or phase imbalance against baseline.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled electrical metrics check
- ActionQuery Datadog power draw and phase metricsDatadog
- LogicDetect spike or phase imbalance vs baseline
- ActionOpen PagerDuty incident for critical circuitPagerDuty
- OutputPost incident summary to Slack ops channelSlack
What it does
This workflow watches your building's electrical telemetry in Datadog and catches power problems before they trip a breaker or damage equipment. On a schedule it queries panel-level power draw and phase balance, compares the latest window against a rolling baseline, and when a circuit sits over its critical threshold it opens a PagerDuty incident so the right engineer is paged immediately. A Slack note gives the wider team context.
When to use it
Use it when electrical metrics already flow into Datadog and you need true escalation — not just a dashboard — for overloaded circuits, failing PDUs, or unbalanced three-phase loads. Best for data-center-adjacent facilities or buildings with critical tenant load.
How it works
- 1A schedule fires the check at your chosen interval.
- 2A Datadog query pulls recent power draw and phase-balance metrics per circuit.
- 3A logic step compares each circuit to its baseline and threshold, flagging sustained spikes or imbalance.
- 4If a circuit is critical, a PagerDuty incident is created with the circuit and measured load.
- 5A Slack message posts the incident summary to the operations channel.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 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
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.