DEVOPS
Turn the war-room Zoom recording into a draft postmortem
When a Zoom incident bridge recording finishes processing, this workflow pulls the transcript, drafts a structured postmortem timeline, files it in Confluence.
How it runs
The automated pipeline, trigger to output.
- TriggerZoom war-room recording completedZoom
- ActionFetch recording transcriptZoom
- ActionDraft structured postmortemOpenAI
- ActionPublish postmortem to ConfluenceConfluence
- OutputLink doc on PagerDuty incidentPagerDuty
What it does
The hardest part of a postmortem is reconstructing what happened. This workflow takes the completed recording of a war-room Zoom call, uses its transcript to draft a structured incident timeline and impact summary, publishes the draft to Confluence, and attaches the link to the PagerDuty incident for the review.
When to use it
Use it after an incident is resolved and the war-room call has ended. It removes the blank-page problem from postmortems by giving the incident commander a populated first draft built from what was actually said on the bridge.
How it works
- 1A Zoom webhook fires when the war-room recording completes processing.
- 2The workflow retrieves the recording transcript from Zoom.
- 3An OpenAI step structures the transcript into a timeline, root-cause hypotheses, and action items in your postmortem format.
- 4Confluence creates a new postmortem page in the incidents space.
- 5PagerDuty receives the published doc link as an incident note for the follow-up review.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
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.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.