TICKET MANAGEMENT
Create Asana follow-up tasks from Zoom call action items linked to the Zendesk ticket
After a Zoom support call, extracts each commitment from the transcript and creates one Asana task per action item.
How it runs
The automated pipeline, trigger to output.
- TriggerZoom recording completedZoom
- ActionFetch transcript and resolve Zendesk ticketZoom
- ActionExtract structured action itemsOpenAI
- ActionCreate one Asana task per action itemAsana
- OutputAdd Zendesk note linking the tasksZendesk
What it does
Converts the verbal promises in a recorded support call into tracked work. Instead of a single summary note, it splits the call into discrete action items and files each one as its own Asana task, so nothing said on the call quietly falls through.
When to use it
Use it when call commitments require real follow-up work owned by engineering, success, or ops rather than a one-line ticket reply. Good for escalations, custom configuration promises, and "we'll get back to you" moments that need an accountable owner and a due date.
How it works
- 1Zoom fires the recording-completed event.
- 2Pull the transcript and locate the related Zendesk ticket by customer email or meeting subject.
- 3OpenAI extracts a structured list of action items, each with a title, owner hint, and priority.
- 4For each extracted item, create an Asana task containing the description, recording link, and Zendesk ticket URL.
- 5Add an internal Zendesk note listing the created tasks so agents see the follow-up trail in one place.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ZendeskTickets, queues, knowledge base.
- 4Connect AsanaTasks, projects, milestones — everywhere.
- 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 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.
