AI AGENTS

Post-Incident WAF Postmortem Enricher for Linear

After a WAF incident resolves, an agent gathers the Cloudflare rule changes and timeline, writes a structured postmortem in Linear, and posts the draft to Slack for review.

CategoryAI Agents
Enginepaperclip
Difficultyintermediate
Triggerwebhook
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerIncident-resolved webhook receivedHTTP webhook
  • ActionRead Cloudflare WAF rule change history for the zoneCloudflareCloudflare
  • ActionFetch applied runbook from MCP serverCustom MCP server
  • LogicAssemble timeline and draft postmortem sections
  • ActionWrite structured postmortem into the Linear issueLinearLinear
  • OutputPost draft link to Slack for reviewSlack

What it does

Closes the loop after a WAF incident. On a resolved-incident signal, an agent pulls the relevant Cloudflare WAF rule history and the runbook that was followed, then assembles a structured Linear postmortem — timeline, root cause hypothesis, actions taken, and follow-ups — instead of leaving an empty stub.

When to use it

Use it when postmortems pile up as unwritten TODOs. This produces a complete first draft from the actual change record so the on-call engineer edits rather than starts from scratch. Pairs well with the remediation agents that opened the stub.

How it works

  1. 1A webhook fires when an incident is marked resolved.
  2. 2The agent reads the Cloudflare WAF rule change history for the affected zone.
  3. 3It fetches the runbook that was applied from the MCP server to reconstruct intent.
  4. 4A logic step assembles the timeline and drafts the postmortem sections.
  5. 5It writes the structured postmortem into the existing Linear issue.
  6. 6It posts the draft link to Slack for the on-call engineer to review and finalize.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CloudflareWorkers, Pages, R2, KV — the edge stack.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  3. 3
    Connect Custom MCP serverConnect any MCP-compatible tool you own.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Connect HTTP webhookTrigger any URL on agent actions.
  6. 6
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  7. 7
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  8. 8
    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.