CUSTOMER SUPPORT
Cluster the week's Zendesk tickets into KB article proposals
On a weekly schedule, groups the past week's resolved Zendesk tickets by recurring theme and proposes one Notion article draft per cluster.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule (Monday)
- ActionPull last 7 days of resolved ticketsZendesk
- ActionCluster tickets into themesOpenAI
- LogicKeep clusters above volume threshold
- ActionDraft one article per clusterOpenAI
- OutputWrite proposals to Notion databaseNotion
What it does
Instead of one article per ticket, this workflow looks at a whole week of resolved tickets, finds the topics that came up most often, and proposes a single consolidated draft for each recurring theme. Editors see exactly which undocumented issues are driving the most support volume.
When to use it
Run it when ticket-by-ticket drafting would bury your editors in near-duplicates. Ideal for teams that want to prioritize documentation by impact, writing the one article that deflects fifty tickets rather than fifty articles nobody reads.
How it works
- 1A weekly schedule kicks off the run every Monday morning.
- 2The flow pulls all tickets resolved in the trailing seven days from Zendesk with their subjects and resolutions.
- 3OpenAI clusters the tickets into themes and ranks each cluster by volume and effort saved.
- 4A logic step keeps only clusters above a minimum ticket count, dropping one-off issues.
- 5For each surviving cluster, OpenAI drafts a consolidated article covering the shared root cause and fix.
- 6Each draft is written to a Notion "KB Proposals" database with its ticket count and example links for the editor to approve.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect OpenAIModels, embeddings, files.
- 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 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.