IT OPS

Weekly Maintenance-Window Compliance Report from Outlook and Datadog

Every week this workflow correlates Outlook maintenance events with Datadog downtimes, scores each window for clean start/stop muting.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly report schedule
  • ActionPull week's Outlook events and Datadog downtime historyDatadogDatadog
  • LogicCorrelate windows to downtimes and score compliance
  • ActionWrite compliance report to NotionNotionNotion
  • OutputPost headline summary to SlackSlack

What it does

Produces a weekly audit of how well maintenance windows were enforced. For each window it checks whether a downtime was created on time, scoped correctly, and cancelled at window end, then grades the result and reports the gaps.

When to use it

Use it for change-management reviews and on-call retros where you need evidence that monitors were muted only during approved windows and un-muted afterward.

How it works

  1. 1A weekly schedule fires the report job.
  2. 2It pulls the past week's `[MAINTENANCE]` Outlook events and the corresponding Datadog downtime history.
  3. 3The flow correlates each window to its downtime and scores start timing, scope accuracy, and clean cancellation.
  4. 4A logic step rolls the per-window grades into a compliance summary and flags any windows with missing or overrunning downtimes.
  5. 5A formatted report is written to a Notion page for the change-management record.
  6. 6Slack posts the headline numbers and a link to the full report.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect DatadogMetrics, traces, log search.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.