PERSONAL PRODUCTIVITY

Daily digest of unaddressed Loom-critique ClickUp tasks

Each morning, scans ClickUp for design-critique tasks created from Loom reviews that are still open past their target.

CategoryPersonal Productivity
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerDaily schedule at configured hour
  • ActionQuery open overdue loom-critique tasks in ClickUpClickUpClickUp
  • LogicGroup overdue tasks by assignee
  • LogicSkip assignees with no overdue tasks
  • OutputDM each owner a digest with Loom timestamp linksSlack

What it does

Feedback captured from Loom critiques can pile up unaddressed. This scheduled workflow checks every morning for design-critique tasks in ClickUp that are still open and overdue, groups them by assignee, and DMs each person a tidy digest — each line links back to the exact Loom moment so they can re-watch the context before acting.

When to use it

When async critique tasks tend to go stale and you want gentle, owner-scoped nudges instead of a noisy channel blast. Keeps the design backlog honest without standups.

How it works

  1. 1A daily schedule trigger fires at the configured hour.
  2. 2ClickUp is queried for open tasks tagged `loom-critique` whose due date has passed.
  3. 3A grouping step buckets the overdue tasks by assignee.
  4. 4A branch skips assignees with an empty bucket so no one gets an empty ping.
  5. 5For each remaining assignee, a personalized digest is composed with task titles and their stored Loom timestamp links.
  6. 6The digest is delivered as a direct message in Slack to each owner.

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.