TICKET MANAGEMENT
ClickUp Duplicate Merge with Slack Approval Gate
Detects a likely duplicate on ticket creation, posts an approval prompt to Slack.
How it runs
The automated pipeline, trigger to output.
- TriggerNew ClickUp task createdClickUp
- ActionIdentify best duplicate candidateOpenAI
- LogicBranch: confidence above threshold?
- ActionPost interactive approval prompt to SlackSlack
- OutputOn approval close duplicate and link to original in ClickUpClickUp
What it does
This workflow turns duplicate detection into a one-click human decision. When a new ClickUp ticket looks like a duplicate, it posts the proposed merge to Slack with Approve and Dismiss actions. On approval, it closes the duplicate, links it to the original, and copies any unique detail forward. Nothing is merged without a person saying yes.
When to use it
Use this when merges are consequential enough that you don't want fully automated closure, but you still want the heavy lifting (detection, summarizing, linking) done for the reviewer.
How it works
- 1A ClickUp task-created webhook fires.
- 2OpenAI compares the new ticket to recent open tickets and identifies the best duplicate candidate.
- 3A logic step continues only if the match clears the confidence threshold.
- 4The flow posts an interactive Slack approval with both tickets summarized.
- 5On approval, the flow closes the duplicate in ClickUp, adds a relationship link to the original, and appends a note recording the merge.
Set it up
What you configure once, before turning it on.
- 1Connect ClickUpDocs + tasks + chats in one workspace.
- 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.