PERSONAL PRODUCTIVITY

Stale Loom Walkthrough Reaper with Owner Nudges

Finds Loom videos older than a set threshold that still sit below a view-count floor, then DMs each video's owner on Slack with a one-click prompt to refresh, retire, or keep…

CategoryPersonal Productivity
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionList Loom videos with age and view countLoomLoom
  • LogicKeep videos past staleness threshold and under view floor
  • ActionResolve owner Slack handle from creator emailSlack
  • OutputDM each owner to refresh, archive, or confirmSlack

What it does

It sweeps your Loom workspace on a schedule, isolates async walkthroughs that have gone stale and under-watched, and pings the person who recorded each one so the backlog never rots silently.

When to use it

Run this when your team relies on Loom for async updates and onboarding, and old recordings pile up unwatched, leaving teammates unsure whether a video is still accurate. Ideal for ops or enablement leads who want owners — not a central admin — to decide each clip's fate.

How it works

  1. 1A weekly schedule fires the run.
  2. 2It lists every Loom video in the workspace with its created date and view count.
  3. 3A filter keeps only videos older than the staleness threshold (e.g. 60 days) that are still under the view floor (e.g. 5 views).
  4. 4For each survivor it resolves the owner's Slack handle from the video's creator email.
  5. 5It sends each owner a direct Slack message naming the stale walkthrough and asking them to refresh, archive, or confirm it is still current.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LoomVideo transcripts, libraries.
  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.