CUSTOMER SUPPORT
Draft and review-route ReadMe articles from solved Zendesk tickets
When a Zendesk ticket is solved, identifies whether the question lacks a ReadMe doc, drafts one from the resolution.
How it runs
The automated pipeline, trigger to output.
- TriggerZendesk ticket solvedZendesk
- ActionExtract question + resolution with OpenAIOpenAI
- ActionSearch ReadMe for existing articleReadMe
- LogicBranch: no adequate article found?
- ActionDraft ReadMe article and save as draftReadMe
- OutputCreate Linear review task for docs ownerLinear
What it does
Converts solved Zendesk tickets into reviewed ReadMe documentation. The workflow detects when a solved ticket covers a topic missing from ReadMe, drafts the article from the agent's resolution, and routes it through a human review gate in Linear so nothing reaches the public docs unchecked.
When to use it
Use it when your public developer or product docs live in ReadMe and support runs in Zendesk, and you want a controlled pipeline that produces drafts automatically but keeps a human approval step.
How it works
- 1A Zendesk ticket is set to solved, triggering the flow.
- 2OpenAI extracts the question and the verified resolution from the ticket thread.
- 3The workflow searches ReadMe for an existing article on the topic.
- 4A branch continues only when no adequate article exists.
- 5OpenAI drafts a ReadMe-formatted article from the resolution.
- 6The draft is saved to ReadMe and a Linear review task is created for the docs owner.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect ReadMeAPI docs, changelog, auth.
- 4Connect LinearIssues, projects, cycles, triage.
- 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 Customer Support workflows
Send a tailored Loom onboarding sequence on Front first-reply
When a new customer's first email lands in Front, this picks the Loom onboarding walkthroughs matching their plan and use case, builds a friendly sequenced reply.
Suggest the right Loom video by classifying Intercom message intent
Reads each new inbound Intercom conversation, classifies what the customer is trying to do, and surfaces the best-matching Loom walkthrough to the agent as an internal note.
Draft personalized fix-live replies for support to review
When a Sentry issue resolves, an agent reads each linked ticket's full thread and drafts a tailored 'your fix is live' reply per requester.
Close the loop with requesters when a Linear bug moves to Done
When a Linear issue created from a support escalation moves to Done after deploy, look up the originating Zendesk tickets and notify each requester that their reported bug is…
Reopen and notify Front conversations when their bug fix deploys
When a deploy resolves a Sentry issue, find the snoozed or closed Front conversations linked to it, reopen them, and send the customer a reply that the fix is now live.
Tell Intercom users their reported bug shipped after a Vercel deploy
On a successful Vercel production deployment, match the release's resolved Sentry issues to Intercom conversations and message each affected user that their reported issue is…
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.