SUMMARIZATION
Audience-split release notes: route customer-facing vs internal changes
On each release, this classifies merged PRs as customer-facing or internal, then writes two tailored summaries.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub release publishedGitHub
- ActionFetch merged PRs with labelsGitHub
- ActionClassify each PR: customer-facing vs internalOpenAI
- LogicBranch into customer and internal buckets
- ActionPublish customer changelog note to IntercomIntercom
- OutputPost technical recap as Linear updateLinear
What it does
One release, two audiences. The workflow reads the PRs in a release, decides which changes customers will notice versus which are internal-only, and produces two separately-toned summaries: a friendly, jargon-free note for customers and a precise technical recap for the engineering org.
When to use it
When the same release needs both a public-friendly announcement and an internal record, and you don't want one team's noise leaking into the other's view. Great for product-led teams shipping continuously.
How it works
- 1A GitHub release-published event triggers the flow.
- 2It pulls the merged PRs for the release with their labels and descriptions.
- 3An OpenAI step classifies each PR as customer-facing or internal based on labels and impact.
- 4A logic branch splits the set into two buckets.
- 5The customer-facing bucket is rewritten as a warm changelog note and posted to Intercom.
- 6The internal bucket is summarized technically and written as a Linear project update.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect IntercomConversations, contacts, articles.
- 4Connect LinearIssues, projects, cycles, triage.
- 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.