SUMMARIZATION
Per-Transcript Feature-Request Extractor to Linear
When a new call transcript lands in Drive, extracts explicit feature requests and pain points, then files or de-dupes them as tagged issues in Linear.
How it runs
The automated pipeline, trigger to output.
- TriggerNew transcript file added to Drive folderGoogle Drive
- ActionRead the transcript textGoogle Drive
- ActionExtract structured feature requestsOpenAI
- LogicMatch each request to existing Linear issueLinear
- ActionCreate issue or append customer mentionLinear
- OutputEmit filed-vs-merged summary
What it does
Watches for each new transcript as it arrives and pulls out the concrete product asks buried in the conversation. For every distinct request it either opens a Linear issue or, if a matching one already exists, adds the new customer mention as a comment so demand stacks on a single ticket instead of fragmenting.
When to use it
Use it when you want feature signal captured the moment a call is transcribed, not batched weekly. Good for teams that run product discovery through Linear and want every customer ask traceable back to the call that produced it.
How it works
- 1A new file appearing in the Drive transcripts folder triggers the run.
- 2The transcript text is read.
- 3OpenAI extracts a structured list of feature requests, each with a one-line title, the verbatim quote, and the customer name.
- 4A logic step searches Linear for an existing issue matching each request title.
- 5If found, the new mention is appended as a comment; if not, a new issue is created with the customer-requests label.
- 6The flow emits a short summary of what was filed versus merged.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 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.