PERSONAL PRODUCTIVITY
Unwatched Loom Backlog to Notion Triage Register
Builds and maintains a Notion database of every Loom walkthrough that has gone stale and unwatched, tagging each with age, view count, and a suggested action so a reviewer can…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionPull all Loom videos with metadataLoom
- LogicFilter stale, under-watched videos
- LogicCompute suggested action from view band
- ActionUpsert one row per video into Notion registerNotion
- OutputPost Slack summary linking the registerSlack
What it does
It turns the scattered list of neglected Loom recordings into a single Notion triage register, upserting one row per stale video with the metadata a reviewer needs to decide keep, update, or kill.
When to use it
Use it when nudging individual owners is not enough and you want a durable, sortable backlog of every aging walkthrough that a documentation or enablement owner reviews in a standing session. Good for teams that triage content debt in a recurring meeting rather than ad hoc.
How it works
- 1A schedule triggers the sweep each week.
- 2It pulls all Loom videos with created date, owner, and view count.
- 3A filter selects videos older than the threshold and below the view floor.
- 4A logic step computes a suggested action — "retire" for near-zero views, "refresh" for moderately watched — based on the view band.
- 5It upserts a row per video into the Notion triage database, keyed by Loom video ID so reruns update rather than duplicate.
- 6It posts a Slack summary linking the register and the count of new items needing triage.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect NotionPages, databases, comments.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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 Personal Productivity workflows
Log Outlook promises to Airtable with per-recipient commitment rollups
Captures promises from sent Outlook mail into an Airtable base, linking each commitment to a recipient record so you get a running per-contact view of everything you've promised…
Turn Outlook email promises into assigned Asana tasks with due dates
When you send an email containing a commitment, an LLM extracts the promise and its deadline and creates a corresponding Asana task assigned to you with the due date set.
Auto-decline low-priority invites that collide with deep-work blocks
When a new calendar invite lands on top of a protected deep-work block, an AI scores its priority and auto-declines low-value meetings with a polite note proposing alternative…
Decline focus-block meetings and auto-propose a free slot via Notion log
When a low-priority invite hits a focus block, it declines the meeting, finds your next genuinely free slot, replies with a counter-proposal.
Monthly Meeting Cost Report by Email
On the first of each month, tallies every recurring meeting's total person-hours across the team, converts to an estimated dollar cost.
Auto-create weekly focus blocks around existing meetings and guard them
Every Sunday an agent reads next week's confirmed meetings, carves protected deep-work blocks into the open gaps, sets your Slack status to defend them.
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.