IT OPS

Deferred Alert Watch-List to Notion Handoff Page

On a schedule, collects Datadog alerts that were snoozed or muted and Sentry issues marked ignored.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSchedule runs at shift boundary
  • ActionQuery muted/downtime Datadog monitorsDatadogDatadog
  • ActionQuery ignored/snoozed Sentry issuesSentrySentry
  • LogicDrop expired deferrals, flag soon-to-resurface
  • OutputUpsert watch-list into Notion handoff pageNotionNotion

What it does

Deferred work is the easiest thing to lose between shifts. This builds a living watch-list of every alert someone silenced and every Sentry issue someone snoozed, with the reason and the time it will resurface, and writes it to a shared Notion page the team treats as the running handoff log.

When to use it

Use it when your operators mute noisy monitors or ignore known-issue Sentry events during a shift and you need the next person to understand what was intentionally parked versus what slipped through.

How it works

  1. 1A schedule runs at each shift boundary.
  2. 2Query Datadog for monitors currently in a muted or downtime state, capturing the mute reason and expiry.
  3. 3Query Sentry for issues set to ignored or snoozed, capturing the snooze window.
  4. 4A logic step filters out anything whose deferral has already expired and flags items resurfacing in the next shift.
  5. 5Render the remaining items into a table grouped by resurface time.
  6. 6Upsert the table into the dedicated Notion handoff page, replacing the prior shift's block.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DatadogMetrics, traces, log search.
  2. 2
    Connect SentryErrors, performance, releases.
  3. 3
    Connect NotionPages, databases, comments.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.