OTHER

Weekly Loom Standup Morale Trend Report in Notion

Once a week, gathers all of the team's Loom standup transcripts from the past seven days, computes a morale trend and recurring-blocker themes.

CategoryOther
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionCollect week's Loom transcriptsLoomLoom
  • ActionCompute morale trend + recurring themes with OpenAIOpenAI
  • LogicRank persistent blockers and set trend direction
  • OutputPublish weekly report page in NotionNotionNotion

What it does

Produces a weekly written pulse on team health from a week of async standups. Instead of a single-day snapshot, it looks across all standups in the trailing week to surface morale direction, recurring blockers, and people who have flagged the same problem multiple days running.

When to use it

Use it for a Friday or Monday leadership review when you want evidence-based trends rather than vibes. Best for managers who need a durable, shareable record of how morale and blockers moved week over week.

How it works

  1. 1A weekly schedule triggers the workflow.
  2. 2The week's Loom standup recordings are collected and their transcripts fetched.
  3. 3OpenAI computes a per-day morale score, identifies recurring blocker themes, and detects repeat-mention patterns across the week.
  4. 4A logic step assembles the trend (up, flat, or down) and ranks the persistent blockers.
  5. 5A formatted report page is created in Notion under the leadership space, ready to share in the weekly review.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LoomVideo transcripts, libraries.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect NotionPages, databases, comments.
  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.