SUMMARIZATION
Route a support Loom into a Zendesk help-article or macro draft
Transcribes a support-team Loom walkthrough and, based on its tag, either drafts a public help-center article or an internal macro reply in Zendesk for an agent to review…
How it runs
The automated pipeline, trigger to output.
- TriggerNew support Loom recording detectedLoom
- ActionFetch transcript and chapters from LoomLoom
- LogicBranch on tag: public article vs internal macro
- ActionDraft article or macro from transcript
- OutputCreate unpublished Zendesk draft for agent reviewZendesk
What it does
When a support agent records a Loom showing how to resolve an issue, this workflow transcribes it and decides where it belongs: a customer-facing help article or an internal agent macro. It produces a ready-to-edit draft in Zendesk with the steps written out and the Loom embedded for reference.
When to use it
Your support team solves the same issues repeatedly and captures fixes on Loom. Use this to convert that tribal knowledge into reusable help content and macros without an agent rewriting every clip by hand.
How it works
- 1A new Loom appears in the support team's recording space, triggering the workflow.
- 2Loom returns the transcript plus chapter timestamps.
- 3A logic step reads the video's tag or title prefix to decide the destination: `public` versus `internal`.
- 4An agent step (Paperclip) rewrites the transcript into the right register — friendly help-article steps or terse internal macro instructions — keeping timestamped links to the relevant moments.
- 5The draft is created in Zendesk as an unpublished help-center article or a draft macro, assigned to the recording agent for final review.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect ZendeskTickets, queues, knowledge base.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Summarization workflows
On-submit Loom standup roll-up archived to Confluence
When a standup video is submitted via webhook, transcribes it, generates a per-person written summary, and appends it to a running team standup page in Confluence.
Front Escalation Handoff Doc in Notion
When a Front escalation closes, drafts a structured handoff document in Notion capturing the resolution, customer commitments, and open follow-ups, then alerts the AE in Slack.
Front Escalation War-Room Brief to Slack
On a Front escalation, posts a concise threat-assessment brief to a Slack channel only when the AI judges the situation high-severity.
VIP Front Escalation Instant Exec Page-Out
Detects escalations from VIP accounts in Front, generates a one-paragraph executive recap, and pages the named account exec via Slack and Salesforce task within minutes.
Release health note per Vercel deploy
When a Vercel deploy goes live, summarizes the Sentry errors observed in the release window into a plain-English health note that separates brand-new error classes…
Rollback recommendation when a deploy spikes errors
When a Sentry alert fires for an error spike, attributes it to the most recent deploy, summarizes whether the spike is dominated by new error classes introduced by that release.
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.