SUMMARIZATION
CAB Feature Requests to Deduplicated Linear Backlog Entries
Extracts explicit feature requests from a CAB Zoom recording, checks each against existing Linear issues.
How it runs
The automated pipeline, trigger to output.
- TriggerZoom recording completed for CAB meetingZoom
- ActionExtract discrete feature requests from transcriptOpenAI
- ActionSearch Linear backlog for matching open issueLinear
- LogicBranch: existing match vs. new request
- ActionComment customer evidence and bump priority on matchLinear
- OutputCreate fresh cab-sourced Linear issue for new asksLinear
What it does
This workflow narrows the lens to explicit feature asks. From a CAB Zoom recording it extracts each concrete feature request, searches the Linear backlog for an existing matching issue, and either appends the new customer as evidence on the existing issue or creates a new backlog entry. It prevents duplicate tickets while compounding demand signal on real ones.
When to use it
Use it when your CAB calls generate lots of feature requests and your backlog is already cluttered with near-duplicates. It keeps one canonical issue per ask and tracks which customers requested each.
How it works
- 1A Zoom recording-completed event triggers the workflow.
- 2The transcript is fetched and an LLM extracts a clean list of discrete feature requests with the requesting customer's context.
- 3For each request, the workflow searches Linear for a semantically matching open issue.
- 4A logic branch decides: if a match exists, comment on it with the new customer evidence and bump priority; if not, route to creation.
- 5New requests become fresh Linear issues tagged 'cab-sourced'.
- 6A summary of matched-vs-new outcomes is returned for review.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 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
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.