SUMMARIZATION
Teams recording to Linear engineering issues
When a Microsoft Teams meeting recording is ready, summarizes the discussion and opens a Linear issue for each engineering action item, labeled and assigned by the AI.
How it runs
The automated pipeline, trigger to output.
- TriggerTeams meeting recording readyMicrosoft Teams
- ActionFetch meeting transcriptMicrosoft Teams
- ActionSummarize and extract engineering action itemsOpenAI
- LogicFilter out non-actionable items
- ActionPost recap to Teams channelMicrosoft Teams
- OutputCreate Linear issue per action itemLinear
What it does
Converts engineering and planning meetings recorded in Microsoft Teams into actionable Linear issues. It writes a recap and creates a tracked issue for every technical follow-up, with a suggested label, priority, and assignee.
When to use it
Use it for sprint planning, architecture reviews, or incident retros held over Teams, where verbal decisions need to become tracked work without someone transcribing tickets by hand.
How it works
- 1A Microsoft Teams trigger fires when a meeting recording and transcript are available.
- 2The transcript is fetched.
- 3OpenAI summarizes the discussion and extracts engineering action items, each with a proposed title, description, label, priority, and owner.
- 4A filter drops non-actionable chatter so only concrete tasks proceed.
- 5The recap is posted back to the Teams channel for visibility.
- 6Each surviving action item is created as a Linear issue in the team's project, assigned and labeled.
Set it up
What you configure once, before turning it on.
- 1Connect Microsoft TeamsChannels, chats, 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.