TICKET MANAGEMENT
Nightly Duplicate-Ticket Cluster Report from Postgres to Email
Runs each night to cluster the day's open tickets stored in Postgres into likely-duplicate groups and emails support leads a digest of the clusters to merge.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule fires
- ActionQuery today's open tickets from PostgresPostgres
- ActionCluster tickets by root issue with OpenAIOpenAI
- LogicProceed only if a duplicate cluster exists
- ActionFormat the clusters into a digest
- OutputEmail merge-candidate digest to leadsGmail
What it does
Produces a once-a-day backstop for duplicates that slipped past real-time checks. It reads the day's open tickets from your Postgres store, groups them into clusters that look like the same underlying issue, and emails leads a prioritized digest of merge candidates.
When to use it
Use it when tickets live in your own database (or a synced mirror) and you want a human-reviewed sweep rather than per-ticket automation. Great for catching duplicates that arrived through different channels.
How it works
- 1A nightly schedule triggers the flow.
- 2Query Postgres for tickets created or updated today that are still open.
- 3Send the batch to OpenAI to cluster tickets by shared root issue and rank clusters by size.
- 4Branch: only build a report if at least one multi-ticket cluster exists.
- 5Format the clusters into a readable digest with ticket IDs, requesters, and suggested primary ticket.
- 6Email the digest to the support leads distribution list via Gmail.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect GmailRead, draft, send, label.
- 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.