SUMMARIZATION
Turn Recurring Feature-Gap Objections from Sales Calls into Linear Issues
Weekly, mines Zoom sales transcripts for objections that are really missing-feature requests, deduplicates them against existing Linear issues.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionCollect past-week Zoom transcriptsZoom
- ActionExtract + cluster feature-gap objections (LLM)OpenAI
- ActionSearch existing Linear issues for matchesLinear
- LogicDecide create-new vs update-existing per cluster
- OutputCreate issues or upvote-comment in LinearLinear
What it does
Each week it reads the latest Zoom sales-call transcripts and isolates only the objections that are actually product feature gaps ("it can't do X," "we need Y integration"). It clusters them, checks each cluster against open Linear issues, and either creates a new issue or adds a weighted comment to an existing one with the deal context and frequency, so product prioritization reflects real revenue-blocking demand.
When to use it
When sales hears the same "missing feature" objection repeatedly but it never reaches product in a structured, deduplicated way.
How it works
- 1A weekly schedule triggers the run.
- 2The Zoom step collects the past week's call transcripts.
- 3An OpenAI step extracts only feature-gap objections and clusters them into requests.
- 4A Linear step searches for matching existing issues.
- 5A logic step decides create-new versus update-existing per cluster.
- 6A Linear step files new issues or comments on matches with frequency and deal value.
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.