ENGINEERING
Loom Bug Video to GitHub Issue with Repro Steps
When a Loom recording is shared, transcribes it, extracts numbered reproduction steps and expected vs actual behavior, and opens a structured GitHub issue with the video embedded.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom video shared in workspaceLoom
- ActionFetch Loom transcript and metadataLoom
- ActionExtract repro steps + expected/actual via LLMOpenAI
- LogicRequire minimum fields (steps + actual behavior)
- OutputCreate structured GitHub issue with embedGitHub
What it does
Turns a raw Loom bug-report video into a clean, engineer-ready GitHub issue. It pulls the transcript, uses an LLM to extract the exact reproduction steps, expected behavior, and observed behavior, then files an issue that follows your bug template with the Loom embedded for context.
When to use it
Use it when teammates, support, or beta users report bugs by recording a quick Loom instead of writing a ticket. It removes the manual step of an engineer watching the video and hand-writing the issue, and guarantees every report lands in the same structured format.
How it works
- 1A new Loom video in the watched workspace triggers the flow.
- 2The flow fetches the video transcript and metadata from Loom.
- 3An OpenAI step parses the transcript into numbered repro steps, expected vs actual behavior, and a one-line title, and flags missing details.
- 4A logic step checks the report has at least the minimum fields (steps + actual behavior) before proceeding.
- 5A GitHub action creates an issue using the bug template, with the Loom link embedded and labels applied.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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.