IT OPS

Require Slack Approval Before Muting Datadog for an Outlook Window

Before a maintenance window can mute production monitors, this workflow posts the request to Slack for a change-approver to approve or reject.

CategoryIT Ops
Enginesim
Difficultyadvanced
Triggerschedule
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled pre-window check pulls Outlook eventOutlook
  • ActionPost approve/reject request to SlackSlack
  • LogicWait for decision; branch approved vs rejected
  • ActionSchedule Datadog downtime when approvedDatadogDatadog
  • OutputLog decision and outcome to NotionNotionNotion

What it does

Adds a human gate to maintenance muting. When a window is about to start, it asks a change-approver in Slack to sign off; approval schedules the Datadog downtime, rejection cancels the action and logs the decision.

When to use it

Use it for production-impacting windows where policy requires a named approver before monitors are silenced, rather than auto-muting on the calendar alone.

How it works

  1. 1A scheduled check runs shortly before each `[MAINTENANCE]` Outlook event and pulls its details.
  2. 2Slack posts an interactive approve/reject request to the change-management channel, naming the window, scope, and requester.
  3. 3The flow waits for the approver's response.
  4. 4A branch routes on the decision: approved versus rejected or timed out.
  5. 5If approved, Datadog schedules the downtime for the scoped monitors over the window duration.
  6. 6Either way the outcome — approved-and-muted or rejected — is written to a Notion change log for audit.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect DatadogMetrics, traces, log search.
  4. 4
    Connect NotionPages, databases, comments.
  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.