ENGINEERING
Dropped Recording to Linear Issues for Engineering Standups
When a meeting audio or video file lands in a Google Drive folder, transcribe it, extract engineering action items, and open Linear issues assigned to the right teammate.
How it runs
The automated pipeline, trigger to output.
- TriggerNew recording in Drive folderGoogle Drive
- ActionDownload and transcribe audioOpenAI
- ActionExtract action items and priorityOpenAI
- LogicMap owners to Linear users and team
- ActionCreate assigned Linear issuesLinear
- OutputReturn created issue IDsLinear
What it does
Watches a Google Drive folder for new meeting recordings, transcribes the audio with OpenAI, extracts technical action items, and creates Linear issues with assignees, priority, and the relevant team. Works for any recording, not just Zoom cloud.
When to use it
For engineering standups, incident retros, and architecture reviews where the recording is uploaded manually rather than captured by Zoom cloud. Turns spoken commitments into trackable Linear work.
How it works
- 1A Google Drive new-file trigger fires when a recording is added to the watched folder.
- 2The flow downloads the file and sends the audio to OpenAI for transcription.
- 3A second OpenAI call extracts action items with owner, priority hint, and a one-line issue title.
- 4A logic step maps owner names to Linear users and infers the target team from keywords.
- 5Each action item becomes a Linear issue with assignee, priority, and team set.
- 6The created issue identifiers are returned as the output.
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 Engineering workflows
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
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.