ENGINEERING
Loom Bug Video Enriched with Sentry Errors into GitHub
An agent transcribes a Loom bug video, pulls matching Sentry errors and stack traces from the same timeframe.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom bug video sharedLoom
- ActionFetch transcript + timestampLoom
- ActionDerive repro + error signatures via LLMOpenAI
- ActionQuery Sentry for matching errorsSentry
- LogicAssess confidence of error match
- OutputOpen GitHub issue with repro + Sentry eventsGitHub
What it does
Fuses a human bug report with machine telemetry. The agent watches for a Loom bug video, extracts the repro steps and the time the user hit the issue, queries Sentry for errors that match the symptom and window, and opens a GitHub issue that pairs the user's reproduction steps with the actual stack traces and event counts.
When to use it
Use it when a Loom alone doesn't give engineers enough to debug and you want the corresponding exception data attached automatically. It turns a vague "this broke" video into a triaged issue backed by concrete error evidence.
How it works
- 1A new Loom bug video triggers the agent.
- 2The agent fetches the transcript and recording timestamp from Loom.
- 3An OpenAI reasoning step derives repro steps and likely error signatures.
- 4A Sentry action queries for matching errors within the recording's timeframe.
- 5A logic step weighs whether the Sentry hits are a confident match.
- 6The agent opens a GitHub issue combining repro steps, the Loom, and the linked Sentry events.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SentryErrors, performance, releases.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
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.
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.
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.
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…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.