DEVOPS
Incident Resolved to Status Update and Postmortem Draft
When a PagerDuty incident resolves, post a customer-facing status update via webhook, then auto-draft a postmortem in Confluence from the incident timeline and Slack thread.
How it runs
The automated pipeline, trigger to output.
- TriggerPagerDuty incident resolvedPagerDuty
- ActionPull incident timeline and resolution durationPagerDuty
- ActionPost customer status update via webhookHTTP webhook
- ActionRead Slack incident thread for remediation notesSlack
- LogicDraft structured postmortem with LLMOpenAI
- OutputCreate Confluence postmortem page for reviewConfluence
What it does
Closes the loop after an incident is resolved. It publishes a clear resolution update to your status page through a webhook, then drafts a structured postmortem by stitching together the PagerDuty timeline and the Slack incident thread, so the writeup is 80 percent done before anyone sits down.
When to use it
Use it when postmortems slip because nobody wants to reconstruct the timeline after the fire is out, and when customers need a prompt, consistent resolution notice.
How it works
- 1PagerDuty marks an incident as resolved and posts the webhook.
- 2The flow pulls the incident timeline: trigger time, acknowledgements, and resolution duration.
- 3An HTTP webhook posts a customer-facing resolution update to the status page.
- 4The linked Slack incident thread is read to capture responder discussion and remediation steps.
- 5An LLM drafts a postmortem with impact, timeline, root cause, and action items.
- 6The draft is written to a new Confluence page in the incidents space for review and sign-off.
Set it up
What you configure once, before turning it on.
- 1Connect PagerDutyIncidents, on-call, escalations.
- 2Connect HTTP webhookTrigger any URL on agent actions.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Connect OpenAIModels, embeddings, files.
- 5Connect ConfluenceSpaces, pages, blueprints.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.