TICKET MANAGEMENT
Archive Zoom support recordings to R2 and log a searchable action-item index per Zendesk ticket
Downloads each completed Zoom support recording to R2 cold storage, writes a row of extracted action items and metadata to Postgres keyed by Zendesk ticket.
How it runs
The automated pipeline, trigger to output.
- TriggerZoom recording completedZoom
- ActionDownload recording and transcriptZoom
- ActionUpload recording to R2 archiveCloudflare R2
- ActionExtract action items and metadataOpenAI
- ActionInsert indexed row into PostgresPostgres
- OutputNote archive link on Zendesk ticketZendesk
What it does
Builds a durable, searchable archive of support calls. Each recording is copied off Zoom into your own R2 bucket, its action items and metadata are written to a Postgres index keyed by the Zendesk ticket, and the ticket gets a permanent archive link. The result is a queryable record that survives Zoom's retention window.
When to use it
Use it when compliance, retention, or analytics needs outlast Zoom's auto-delete policy, or when you want to run SQL across call action items ("every call that promised a refund last quarter"). Good for regulated teams and ops leads who report on call outcomes.
How it works
- 1Zoom fires the recording-completed event.
- 2Download the recording file and transcript from Zoom.
- 3Upload the recording to an R2 bucket with a ticket-scoped object key.
- 4OpenAI extracts action items and structured metadata from the transcript.
- 5Insert a row into Postgres linking the Zendesk ticket ID, R2 URL, and action items.
- 6Post the durable archive link as an internal note on the Zendesk ticket.
Set it up
What you configure once, before turning it on.
- 1Connect ZoomMeetings, recordings, transcripts.
- 2Connect Cloudflare R2Object storage, S3-compatible.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect PostgresAny Postgres URL — query, write, migrate.
- 5Connect ZendeskTickets, queues, knowledge base.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Ticket Management workflows
Deduplicate Discord bug reports against existing Linear issues
Before creating anything, searches Linear for issues matching a new Discord bug report; if a duplicate exists it comments and links the report there, otherwise it opens a fresh…
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.
Promote a Discord message to a Linear issue via an emoji reaction
When a moderator adds a designated emoji reaction to any Discord message, an LLM converts that message into a structured Linear issue and threads the link back.
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.
Route Discord bug reports by severity to Linear or PagerDuty
Classifies each Discord bug report by severity using an LLM, then files normal bugs as Linear issues while escalating critical outages to a PagerDuty incident so on-call gets…
Triage Discord bug threads into structured Linear issues with repro checklists
Watches a Discord bug-report channel, uses an LLM to extract a clean title, severity, and step-by-step reproduction checklist from the messy thread.
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.