IT OPS

Post-Incident → Intercom + Datadog Timeline Compiled to Notion

After an incident resolves, it stitches together the first Intercom outage report, Datadog monitor events.

CategoryIT Ops
Enginesim
Difficultyintermediate
Triggerwebhook
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDatadog incident-resolved webhookDatadogDatadog
  • ActionFetch monitor event history for incident windowDatadogDatadog
  • ActionFind first + peak Intercom outage reportsIntercomIntercom
  • LogicCompute detection gap, impact duration, volume
  • OutputCreate Notion postmortem timeline pageNotionNotion

What it does

Builds the factual backbone of a postmortem automatically. When a Datadog incident closes, it reconstructs the timeline by pairing the earliest customer outage report in Intercom with the monitor's fire and recovery events, then writes a structured timeline page to Notion for the team to annotate.

When to use it

When postmortems stall because nobody wants to reassemble "when did customers first notice vs. when did we?" This delivers detection-gap metrics and a clean timeline within minutes of resolution.

How it works

  1. 1A Datadog incident-resolved webhook triggers the flow.
  2. 2A Datadog action fetches the full monitor event history (fired, escalated, recovered) for the incident window.
  3. 3An Intercom action finds the first and peak outage-tagged conversations in that window to mark customer-detected time.
  4. 4A logic step computes time-to-detect gap, customer-impact duration, and report volume.
  5. 5A Notion output creates a postmortem page with the merged timeline and metrics pre-filled.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect DatadogMetrics, traces, log search.
  2. 2
    Connect IntercomConversations, contacts, articles.
  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.