SUMMARIZATION
Daily release-health rollup to Confluence
Each morning, compares the last 24 hours of Sentry activity against the deploys that shipped in that window and publishes a dated release-health page to Confluence summarizing…
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionFetch Sentry issues active in the last 24hSentry
- LogicTag issues as new vs regressed and map to deploys
- ActionCompose the daily release-health narrativeOpenAI
- OutputPublish a dated Confluence pageConfluence
What it does
This workflow produces a daily, durable record of release health. Once a day it gathers the Sentry issues that emerged or regressed in the past 24 hours, maps them to the deploys that shipped during that period, and writes a narrative rollup: which releases were clean, which introduced new error classes, and which reopened old ones. The result is published as a dated Confluence page.
When to use it
Use it when you want a searchable history of release quality rather than ephemeral Slack pings. It is useful for sprint reviews, incident retros, and onboarding, where "what did our deploys do last Tuesday?" needs a real answer.
How it works
A daily schedule kicks off the run. The flow queries Sentry for issues active in the trailing 24-hour window and tags each as new or regressed. It correlates them to the deploys recorded for that window. An OpenAI step composes the day's release-health narrative with per-release sections and a trend line versus the prior day. A new Confluence page is created under a dated parent, linking each issue back to Sentry.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ConfluenceSpaces, pages, blueprints.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Summarization workflows
Daily Front Escalation Digest with Salesforce Rollup
Each morning, sweeps the prior day's escalated Front conversations, summarizes each, enriches with Salesforce account value, and emails account execs a single prioritized digest.
File a Linear ticket for regressed errors after deploy
Detects Sentry issues that regressed in the latest deploy's release window, summarizes what broke and when it was previously fixed.
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.
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.
Summarize the Zoom webinar Q&A and email follow-ups to attendees
After a Zoom webinar ends, extracts every question asked and its answer, builds a clean Q&A recap with timestamped jump links, and emails it to all registered attendees via Gmail.
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.