TICKET MANAGEMENT
Zendesk Nightly Duplicate Consolidation
On a nightly schedule it scans the day's open Zendesk tickets, groups ones describing the same issue, marks all but one as duplicates of a chosen master ticket.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionFetch today's open Zendesk ticketsZendesk
- ActionCluster tickets and pick masters via OpenAIOpenAI
- LogicFilter to clusters with duplicates only
- ActionMark extras as duplicates of master in ZendeskZendesk
- OutputSend merge digest to SlackSlack
What it does
Instead of merging duplicates one at a time, this batch job sweeps the whole open queue once a night, clusters tickets about the same problem, designates one master per cluster, and links the rest to it. Operators wake up to a deduplicated queue and a clear log of what was joined.
When to use it
Use it for high-volume Zendesk queues where real-time merging is impractical and a daily cleanup keeps backlog counts honest before standup.
How it works
- 1A nightly schedule triggers the flow.
- 2The flow fetches all tickets opened or updated that day with an open status.
- 3OpenAI clusters them by issue and names a representative master per cluster.
- 4A logic step filters out singletons so only real clusters proceed.
- 5For each cluster, Zendesk marks the extras as duplicates of the master and applies a `merged` tag.
- 6Slack receives a digest listing each master, its merged ticket IDs, and the new linked count.
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 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.