AI AGENTS
Loom support fix to Zendesk help draft
When a support Loom showing a customer-facing fix is published, drafts a public-ready help article and creates it as a draft in Zendesk Guide.
How it runs
The automated pipeline, trigger to output.
- TriggerNew support Loom recording publishedLoom
- ActionFetch Loom transcriptLoom
- ActionRewrite into customer-facing help articleHugging Face
- ActionCreate draft article in Zendesk GuideZendesk
- OutputNotify support lead in Slack to approveSlack
What it does
Turns a support agent's Loom recording of how to resolve a common issue into a polished, customer-facing help article drafted directly in Zendesk Guide, so the fix becomes self-serve documentation instead of staying in one agent's head.
When to use it
Use it when support agents discover and record fixes faster than your help center gets updated. This converts the internal walkthrough into a public-tone article and routes it to a lead for approval before it goes live to customers.
How it works
- 1A new Loom recording tagged for support triggers the flow.
- 2The agent fetches the transcript of the walkthrough.
- 3A Hugging Face model rewrites the internal explanation into a customer-friendly help article: a clear problem statement, numbered resolution steps, and a 'still stuck?' contact line, stripping internal jargon.
- 4The agent creates the article as an unpublished draft in the relevant Zendesk Guide section.
- 5A Slack message notifies the support lead with the draft link to review wording and publish.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Connect ZendeskTickets, queues, knowledge base.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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.