AI AGENTS
Standup Blocker Escalator to Linear and PagerDuty
When a team member's Loom standup mentions a blocker, it classifies the severity, files a Linear issue for normal blockers.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom standup recordingLoom
- ActionExtract blocker + severity with LLMOpenAI
- LogicBranch on blocker severity
- ActionFile Linear issue for normal blockerLinear
- OutputPage on-call for release-blocking itemPagerDuty
What it does
Turns spoken blockers into tracked, routed work. After each engineer records their Loom standup, this workflow reads the transcript, detects whether a blocker was raised, judges its severity, and routes it: a normal blocker becomes a Linear issue assigned to the relevant owner, while a release-blocking emergency triggers a PagerDuty page so it doesn't wait until tomorrow's standup.
When to use it
When async standups keep surfacing blockers that get forgotten because no one acts on a video. Use this to guarantee every blocker becomes either a tracked ticket or an immediate page.
How it works
- 1A new Loom standup recording from a tracked team member triggers the flow.
- 2An OpenAI step reads the transcript and extracts any blocker with a severity rating.
- 3A logic branch checks severity: skip if none, escalate if release-blocking.
- 4Normal blockers are filed as a Linear issue with owner and context.
- 5Release-blocking ones additionally page on-call through PagerDuty.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect PagerDutyIncidents, on-call, escalations.
- 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 AI Agents workflows
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.
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.
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.
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.
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.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.