PERSONAL PRODUCTIVITY

Archive perpetually-snoozed ClickUp tasks after owner approval

Detects recurring ClickUp tasks snoozed past a threshold, asks each task owner in Slack to confirm via buttons, and archives only the ones approved for cleanup.

CategoryPersonal Productivity
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled audit cadence fires
  • ActionQuery ClickUp for over-snoozed, never-completed recurring tasksClickUpClickUp
  • ActionAsk each owner to approve cleanup via Slack buttonsSlack
  • LogicBranch on owner response: Archive vs Keep
  • ActionArchive approved tasks in ClickUpClickUpClickUp
  • OutputPost archived-vs-kept summary to SlackSlack

What it does

Identifies recurring tasks that have been rescheduled so many times they are effectively abandoned, then asks the owner to approve cleanup before archiving — so nothing important disappears without a human saying yes.

When to use it

Use it when you want to actively shrink a bloated recurring-task backlog but cannot risk auto-deleting tasks. The owner-approval gate makes it safe to run on real boards.

How it works

  1. 1A schedule triggers the audit on a chosen cadence.
  2. 2The flow queries ClickUp for recurring tasks rescheduled more than the configured limit without a single completion.
  3. 3For each flagged task, it sends the owner an interactive Slack message with Archive and Keep buttons plus the snooze count.
  4. 4A branch waits for the response: Keep clears the flag, Archive proceeds.
  5. 5Approved tasks are archived in ClickUp and a confirmation reply is posted back to the owner.
  6. 6A summary of archived versus kept tasks is delivered to the Slack channel.

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
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    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.