TICKET MANAGEMENT
Flag a new ClickUp task as a likely duplicate at creation time
On every new ClickUp task, this searches existing tasks across spaces for a close match and, if found, comments on the new task with the likely original and alerts the creator…
How it runs
The automated pipeline, trigger to output.
- TriggerClickUp task createdClickUp
- ActionFetch candidate open tasks across spacesClickUp
- ActionScore similarity against candidates with an LLMOpenAI
- LogicExit if no candidate clears the threshold
- ActionComment 'possible duplicate' on the new taskClickUp
- OutputDM the creator in SlackSlack
What it does
Catches duplicates the moment they are filed instead of weeks later. When a task is created, it searches open tasks across spaces for a semantic match, and if a strong candidate exists it comments on the new task linking the probable original and pings the creator in Slack so they can close or merge before work starts.
When to use it
Use it when intake volume is high and the same issue gets re-reported across teams. Real-time flagging stops two people from independently picking up the same ticket.
How it works
- 1A ClickUp task-created event triggers the run.
- 2ClickUp returns candidate open tasks from the relevant spaces for comparison.
- 3An OpenAI step scores the new task against candidates and returns the best match plus a confidence score.
- 4A logic step exits quietly when no candidate clears the threshold.
- 5ClickUp posts a 'possible duplicate of' comment on the new task linking the original.
- 6Slack DMs the creator with the match and a one-click link to both tasks.
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.