IT OPS
Detect Overlapping Maintenance Windows Hitting the Same Datadog Monitors
When a new Outlook maintenance event is created, this workflow checks whether its monitor scope overlaps an existing window and warns the requesters in Teams before both windows…
How it runs
The automated pipeline, trigger to output.
- TriggerNew or updated Outlook maintenance eventOutlook
- ActionQuery other windows and Datadog monitor scopesDatadog
- LogicCompute overlap; branch on collision
- ActionWarn both requesters in Microsoft TeamsMicrosoft Teams
- OutputRecord conflict in Notion for resolutionNotion
What it does
Catches scheduling collisions. On a new or updated maintenance event, it compares the event's monitor scope and time range against other windows and surfaces any overlap so two teams don't unknowingly mute the same monitors at once.
When to use it
Use it in busy environments where multiple teams book windows independently and overlapping mutes can hide a real incident under expected maintenance noise.
How it works
- 1A new or updated `[MAINTENANCE]` Outlook event fires the trigger.
- 2The flow parses its monitor scope and start/end times.
- 3It queries other Outlook maintenance events in the same window and computes scope intersections against the Datadog monitor tags involved.
- 4A branch decides: no overlap versus a real scope-and-time collision.
- 5On collision, Microsoft Teams posts a warning to both requesters naming the conflicting windows and shared monitors.
- 6The detected conflict is recorded in Notion so the scheduling owner can resolve it before either window starts.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect Microsoft TeamsChannels, chats, files.
- 4Connect NotionPages, databases, comments.
- 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.