IT OPS
Mute Datadog Monitors at the Start of an Outlook Maintenance Window
When an Outlook calendar event tagged as a maintenance window begins, this workflow downtimes the matching Datadog monitors and posts a change record so on-call doesn't chase…
How it runs
The automated pipeline, trigger to output.
- TriggerOutlook maintenance event startsOutlook
- LogicParse scope; abort if cancelled or empty
- ActionSchedule Datadog downtime for matching monitorsDatadog
- ActionAppend change record to NotionNotion
- OutputPost mute notice to on-call Slack channelSlack
What it does
Reads a scheduled maintenance event from an Outlook calendar, parses the affected scope from the event body, schedules a Datadog downtime for the matching monitors, and records the action in Notion plus a Slack heads-up.
When to use it
Use it when your maintenance windows live in an Outlook team calendar and you want monitor muting to happen automatically at start time instead of an engineer remembering to do it manually.
How it works
- 1An Outlook event whose subject starts with `[MAINTENANCE]` reaches its start time and fires the trigger.
- 2The flow parses the event body for a `scope:` line listing Datadog monitor tags or IDs.
- 3A guard confirms the event is not cancelled and the scope is non-empty; empty scopes abort safely.
- 4Datadog schedules a downtime covering the parsed tags for the event's duration.
- 5A change record (window name, scope, start/end, requester) is appended to a Notion database.
- 6Slack posts a short notice to the on-call channel confirming which monitors are muted and until when.
Set it up
What you configure once, before turning it on.
- 1Connect OutlookMail, calendar, contacts.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect NotionPages, databases, comments.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.