AI & RAG

Auto-draft a Confluence runbook page from clustered postmortems

When an engineer requests a runbook for a service, retrieves all related postmortems, synthesizes a structured runbook.

CategoryAI & RAG
EngineSim + Paperclip
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEngineer requests a runbook for a service via webhookHTTP webhook
  • ActionRetrieve all postmortems for that service from PostgresPostgreSQLPostgres
  • ActionSynthesize a structured runbook with cited incidentsOpenAI
  • ActionCreate a draft runbook page in ConfluenceConfluenceConfluence
  • OutputOpen a Linear ticket linking the draft for reviewLinearLinear

What it does

Generates a first-draft runbook for any service straight from its incident history. An engineer kicks it off with a service name; the flow gathers every related postmortem, distills the common failure modes and proven fixes into a structured runbook, publishes it as a draft Confluence page, and opens a Linear ticket so a human reviews before it goes live.

When to use it

Use it when onboarding a new service to oncall, or when a service has accumulated enough incidents that a written runbook is overdue. It compresses days of doc-writing into a reviewable draft grounded entirely in what actually happened.

How it works

  1. 1A webhook (or internal form) triggers the flow with a target service name.
  2. 2All postmortems tagged to that service are retrieved from the Postgres vector store.
  3. 3The model synthesizes a structured runbook: symptoms, diagnostics, mitigation steps, and escalation, citing source incidents.
  4. 4A draft page is created in the team's Confluence space.
  5. 5A Linear ticket is opened linking the draft and assigned for review and publishing.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect ConfluenceSpaces, pages, blueprints.
  4. 4
    Connect LinearIssues, projects, cycles, triage.
  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.