TICKET MANAGEMENT
Execute an approved ClickUp merge and rewire linked dependencies
When an operator approves a merge in Slack, this closes the duplicate ClickUp tasks, moves their dependencies and links onto the canonical task.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack merge approval receivedHTTP webhook
- ActionRead duplicates' dependencies and links from ClickUpClickUp
- LogicCompute rewire plan, skip self-referential edges
- ActionRepoint dependencies and close duplicates in ClickUpClickUp
- OutputReport rewired edges to SlackSlack
What it does
Turns an approved merge decision into safe ClickUp changes. It reads which task is the keeper and which are duplicates, then repoints every blocking/waiting-on dependency and linked relationship from the duplicates onto the keeper, comments a merge note on each duplicate, and closes them. A summary of every rewired edge goes back to Slack.
When to use it
Use it as the action half of a dedupe workflow once a human has confirmed a merge. It removes the manual, error-prone step of hand-copying dependencies before closing duplicates — the part where links usually get dropped.
How it works
- 1A Slack approval (button or webhook payload) triggers the run with keeper and duplicate task IDs.
- 2ClickUp returns each duplicate's dependencies, linked tasks, and subtasks.
- 3A logic step computes the rewire plan, skipping edges that already point at the keeper to avoid self-loops.
- 4ClickUp applies the new dependencies, adds a merge comment, and sets duplicates to a closed status.
- 5Slack receives a confirmation listing every dependency moved and task closed.
Set it up
What you configure once, before turning it on.
- 1Connect ClickUpDocs + tasks + chats in one workspace.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 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.
