SUMMARIZATION
Draft a release postmortem in Confluence from Sentry health
When a Sentry release is marked as a bad deploy, compiles its error signatures, regression timeline, and crash-rate impact into a pre-filled postmortem page in Confluence ready…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry release flagged bad deploySentry
- ActionPull issues, timeline, and commitsSentry
- ActionFetch linked GitLab commitsGitLab
- ActionDraft postmortem sectionsOpenAI
- OutputCreate pre-filled Confluence pageConfluence
What it does
This workflow jump-starts the postmortem. When a Sentry release is flagged as a problem deploy, it gathers the error signatures, the crash-rate timeline, affected user counts, and the linked commits, then drafts a structured incident write-up as a Confluence page with summary, impact, and timeline sections already filled in.
When to use it
Use it after a rough release when writing the postmortem from scratch is the part nobody wants to start. It produces a solid first draft so the team edits rather than authors from a blank page.
How it works
- 1Sentry fires a webhook when a release is tagged as a bad deploy.
- 2The flow pulls the release's issues, crash-rate timeline, and associated GitLab commits.
- 3An OpenAI step organizes everything into summary, user-impact, root-signature, and timeline sections.
- 4A Confluence page is created from a postmortem template, pre-populated with that content and linked back to Sentry and the commits for review.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect GitLabRepos, MRs, pipelines, registry.
- 4Connect OpenAIModels, embeddings, files.
- 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 Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
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.