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.

CategoryTicket Management
Enginesim
Difficultyadvanced
Triggerwebhook
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSlack merge approval receivedHTTP webhook
  • ActionRead duplicates' dependencies and links from ClickUpClickUpClickUp
  • LogicCompute rewire plan, skip self-referential edges
  • ActionRepoint dependencies and close duplicates in ClickUpClickUpClickUp
  • 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

  1. 1A Slack approval (button or webhook payload) triggers the run with keeper and duplicate task IDs.
  2. 2ClickUp returns each duplicate's dependencies, linked tasks, and subtasks.
  3. 3A logic step computes the rewire plan, skipping edges that already point at the keeper to avoid self-loops.
  4. 4ClickUp applies the new dependencies, adds a merge comment, and sets duplicates to a closed status.
  5. 5Slack receives a confirmation listing every dependency moved and task closed.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ClickUpDocs + tasks + chats in one workspace.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Connect HTTP webhookTrigger any URL on agent actions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.