IT OPS
Unmute Datadog Monitors When the Maintenance Window Ends and Verify Health
At the end of an Outlook maintenance event, this workflow cancels the Datadog downtime, waits for monitors to report.
How it runs
The automated pipeline, trigger to output.
- TriggerOutlook maintenance event endsOutlook
- ActionCancel Datadog downtime for the windowDatadog
- LogicPoll monitor status; branch on clean vs still-firing
- ActionPage on-call if a monitor is still redPagerDuty
- OutputPost window-closed confirmation to SlackSlack
What it does
Closes out a maintenance window: it cancels the Datadog downtime for the scoped monitors, checks their post-window status, and either confirms a clean exit or pages on-call if a monitor came back red.
When to use it
Use it as the bookend to a window-start muter. It guarantees monitors get un-muted on time and catches the case where maintenance left a service unhealthy.
How it works
- 1The Outlook maintenance event reaches its end time and fires the trigger.
- 2The flow reads the downtime ID recorded for that window and cancels the matching Datadog downtime.
- 3It polls the scoped monitors' current status for a short settling period.
- 4A branch evaluates the results: all OK versus one or more still alerting.
- 5If clean, Slack posts a window-closed confirmation to the on-call channel.
- 6If any monitor is still firing, PagerDuty triggers an incident with the window name and the offending monitors attached.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 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
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.