TICKET MANAGEMENT
Transcribe a customer Loom bug walkthrough into a structured Asana task
When a support agent shares a customer's Loom recording of a bug, the workflow transcribes it, has an agent turn the narration into numbered repro steps and environment notes.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Loom recording shared in support workspaceLoom
- ActionFetch Loom transcript and recording metadataLoom
- ActionAgent converts narration into repro steps and env notesOpenAI
- ActionCreate Asana task in engineering project with embedded videoAsana
- OutputTag by severity and assign to triage ownerAsana
What it does
Customers often record a Loom showing a regression instead of writing it up. This workflow grabs the Loom transcript, has the agent convert the spoken walkthrough into clean numbered reproduction steps plus an environment summary, and files an Asana task in the engineering backlog with the video link front and center.
When to use it
Use it when your team collects screen-recorded bug reports and someone has to keep watching the video to remember what happens. It produces a written, searchable task so engineers don't have to scrub through footage.
How it works
- 1A new Loom recording shared to the support workspace triggers the run.
- 2The workflow pulls the recording's transcript and metadata from Loom.
- 3The agent rewrites the narration into ordered repro steps, expected vs. actual behavior, and any environment details mentioned aloud.
- 4An Asana task is created in the engineering project with the structured write-up and the embedded Loom link.
- 5The task is tagged by reported severity and assigned to the triage owner.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect AsanaTasks, projects, milestones — everywhere.
- 3Connect OpenAIModels, embeddings, files.
- 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 Ticket Management workflows
Enrich Discord bug reports with Sentry errors before filing in Linear
Takes a Discord bug report, has an LLM pull out likely error signatures, searches Sentry for matching events.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
Weekly reopen-by-agent coaching digest
Aggregates each agent's solved-then-reopened tickets for the week, identifies the most common reopen reason per agent, and emails a private coaching digest to the support manager.
Escalate repeat reopens to a Linear bug
Detects when the same underlying issue reopens across multiple tickets, uses an AI agent to cluster them by root cause.
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.