AI AGENTS
Weekly call-theme rollup into Linear feature requests
On a weekly schedule, an agent clusters the past week of call transcripts into recurring themes and opens or updates Linear issues for the top recurring requests.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule (Monday AM)
- ActionCollect past week's transcriptsZoom
- ActionCluster mentions into themes by account countOpenAI
- LogicKeep only themes above frequency threshold
- ActionSearch Linear for matching open issueLinear
- OutputCreate or update Linear feature requestLinear
What it does
Once a week it gathers every call transcript from the prior seven days, clusters them into recurring themes, and ranks themes by how many distinct accounts raised them. For each top theme it opens a Linear feature-request issue — or appends new evidence to an existing one — so product sees demand by volume, not by whoever shouted loudest.
When to use it
Use it when individual call notes are too noisy and you want an aggregate view: what are customers actually asking for this week, weighted by how many of them asked.
How it works
- 1A weekly schedule kicks off the run every Monday morning.
- 2The agent collects the past week's Zoom transcripts and their account tags.
- 3It clusters mentions into themes and counts distinct accounts per theme.
- 4A logic step keeps only themes crossing a frequency threshold.
- 5For each surviving theme it searches Linear for a matching open issue.
- 6It updates the matched issue with fresh quotes and account counts, or creates a new feature-request issue when none exists.
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 AI Agents workflows
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Datadog Bill Spike Attribution Agent
When a daily Datadog cost check detects a spend jump, an agent attributes the increase to the specific services and metric types driving it and posts a ranked breakdown to Slack.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
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.