CONTENT CREATION
Turn confused support tickets into doc screenshot fixes
When a support ticket signals a customer is confused by an outdated screenshot, this links the ticket to the offending article, recaptures the current UI.
How it runs
The automated pipeline, trigger to output.
- TriggerNew or updated Zendesk ticket arrivesZendesk
- LogicClassify drift signal and identify implicated article
- ActionRecapture the live documented screenBrowserbase
- ActionStage corrected image as a draft in NotionNotion
- OutputAdd internal note linking the queued fix to the ticketZendesk
What it does
Watches Zendesk for tickets that indicate a doc screenshot no longer matches the product ("the button isn't there," "my screen looks different"). It identifies the referenced article, recaptures the live screen, and stages the corrected image so the same confusion stops recurring.
When to use it
Use it to close the loop between support pain and docs maintenance, so recurring "the docs are wrong" tickets actually drive a fix instead of being answered one customer at a time.
How it works
- 1A new or updated Zendesk ticket triggers the workflow.
- 2A logic step classifies whether the ticket signals screenshot/UI drift and which article is implicated.
- 3Non-drift tickets are dropped; drift tickets continue.
- 4Browserbase recaptures the live version of the documented screen.
- 5The fresh capture replaces the stale image in the Notion article as a draft pending review.
- 6The originating Zendesk ticket gets an internal note linking the queued doc fix.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect NotionPages, databases, comments.
- 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 Content Creation workflows
On-demand: turn a blog URL into narrated B-roll clips
Accepts a blog URL via webhook, scrapes the article, generates a B-roll clip per paragraph with Replicate and a voiceover with ElevenLabs.
Sync a Figma master frame into localized hero renders
Pulls the current master hero frame and its text layers from Figma, generates a localized image variant for each locale defined in Airtable.
Build a Dropbox B-roll library from exported blog drafts
Triggers when a new blog draft file lands in a Dropbox folder, generates a Replicate B-roll clip for each paragraph.
Generate B-roll clips when a blog post is marked Ready in Notion
Watches a Notion blog database for posts flipped to 'Ready', splits the body into paragraphs, and generates a short B-roll video clip for each paragraph with Replicate.
Weekly: clip last week's top blog paragraph and post to socials
Runs on a weekly schedule, picks the highest-traffic paragraph from the past week's posts, generates one polished B-roll clip with Replicate.
On-Demand Screenshot Freshness Report from a Slack Command
A writer requests a freshness check in Slack for a specific docs page; the workflow inspects every screenshot on that page, scores each by age and version gap.
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.