TICKET MANAGEMENT
Merge ClickUp Duplicates on a /dedup Comment Command
When an agent comments a /dedup command on a ClickUp task, the workflow finds the best matching ticket, merges context, links the two, and replies with the result.
How it runs
The automated pipeline, trigger to output.
- TriggerClickUp comment with /dedup commandClickUp
- ActionFetch candidate open ticketsClickUp
- ActionRank match and draft consolidated summaryOpenAI
- LogicBranch: usable match found?
- OutputLink related tasks and reply in comment threadClickUp
What it does
This workflow gives agents an on-demand dedup command. Whenever someone comments `/dedup` on a ClickUp task, it searches for the closest matching open ticket, consolidates the unique context from both, links them as related, and replies in the comment thread with what it did. Detection runs only when an agent explicitly asks, keeping it precise and intentional.
When to use it
Use this when agents prefer to invoke deduplication manually during triage rather than have it fire on every new ticket. Ideal for teams that want a deliberate, agent-driven control.
How it works
- 1A ClickUp comment webhook fires and the flow detects the `/dedup` command on a task.
- 2The flow fetches candidate open tickets from the same list.
- 3OpenAI ranks candidates and drafts a consolidated context summary for the top match.
- 4A logic step verifies a usable match exists before acting.
- 5The flow links the two tasks as related in ClickUp and replies in the comment thread with the matched ticket and merge summary.
Set it up
What you configure once, before turning it on.
- 1Connect ClickUpDocs + tasks + chats in one workspace.
- 2Connect OpenAIModels, embeddings, files.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.