CUSTOMER SUPPORT
Weekly top-gaps digest from Zendesk to Slack
Each Monday, ranks the past week's recurring unanswerable questions across Zendesk and posts a prioritized digest to Slack so the docs owner can pick what to write next.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly Monday schedule
- ActionFetch last 7 days of Zendesk ticketsZendesk
- ActionFlag unanswered tickets and extract questions (OpenAI)OpenAI
- LogicGroup into themes; rank by frequency and priority
- ActionDraft the top-10 gaps digest (OpenAI)OpenAI
- OutputPost the ranked digest to SlackSlack
What it does
This workflow gives your team a weekly readout of where the documentation is failing customers. It pulls the past seven days of Zendesk tickets, uses an LLM to identify which questions were never satisfactorily answered, ranks the recurring themes by volume and customer impact, and posts a ranked top-ten digest to a Slack channel with ticket counts and example links.
When to use it
Use it for a standing weekly ritual — a docs standup or support sync — where someone decides what to write next. It complements real-time logging by giving leadership a digestible, prioritized view instead of a raw backlog. Best when your team lives in Slack.
How it works
- 1A weekly schedule fires every Monday morning.
- 2Zendesk returns the trailing seven days of tickets with tags and resolution status.
- 3An OpenAI step flags tickets that closed without a real answer and extracts each underlying question.
- 4A logic step groups questions into themes and ranks them by frequency and ticket priority.
- 5OpenAI drafts a concise, skimmable digest of the top ten gaps.
- 6The digest is posted to the chosen Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect ZendeskTickets, queues, knowledge base.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.
