TICKET MANAGEMENT
Nightly Zendesk Duplicate-Cluster Digest to Notion
Runs every night to scan the day's open Zendesk tickets, cluster near-identical ones.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionFetch last 24h of open Zendesk ticketsZendesk
- ActionEmbed + cluster tickets with confidence scoresOpenAI
- LogicDrop low-confidence clusters, rank the rest
- OutputPublish ranked cluster digest to NotionNotion
What it does
Once a day this workflow sweeps open Zendesk tickets, groups them into duplicate clusters by semantic similarity, and writes a Notion page that lists each cluster, its proposed canonical ticket, and a confidence score. Agents review the digest in the morning and merge with full context instead of hunting for dupes one by one.
When to use it
When real-time merging is overkill but duplicate sprawl still hurts. A scheduled digest fits teams that prefer a daily triage ritual over per-ticket interrupts, and want a written audit trail of what was proposed.
How it works
- 1A nightly schedule triggers the run.
- 2Zendesk returns all tickets opened or updated in the last 24 hours that are still open.
- 3OpenAI embeds each ticket and a clustering step groups them, computing a per-cluster confidence score.
- 4A logic step drops clusters below the threshold and ranks the rest by size and severity.
- 5OpenAI names a canonical ticket per cluster and summarizes the shared root cause.
- 6A formatted digest is published to a Notion database, one row per cluster, ready for morning triage.
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 Ticket Management workflows
Enrich Discord bug reports with Sentry errors before filing in Linear
Takes a Discord bug report, has an LLM pull out likely error signatures, searches Sentry for matching events.
Front-to-Linear Recurring Bug Linker
When a Front ticket is tagged as a bug, it searches Linear for an existing matching issue and either links the ticket to that parent issue or opens a new tracked one.
Front Duplicate Conversation Clusterer
When a new Front conversation arrives, it semantically compares the report against open conversations.
Intercom Known-Issue Auto-Responder
When a new Intercom conversation matches a known active incident, it attaches the conversation to that incident's parent ticket and sends the customer the current status reply.
Weekly reopen-by-agent coaching digest
Aggregates each agent's solved-then-reopened tickets for the week, identifies the most common reopen reason per agent, and emails a private coaching digest to the support manager.
Escalate repeat reopens to a Linear bug
Detects when the same underlying issue reopens across multiple tickets, uses an AI agent to cluster them by root cause.
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.