SUMMARIZATION

Weekly digest of Loom walkthroughs rolled up in Coda and shared to Slack

On a weekly schedule, gathers the week's Loom recordings, transcribes and summarizes each, compiles a single themed digest in Coda, and posts the digest link to a Slack channel.

CategorySummarization
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionList Loom recordings from past weekLoomLoom
  • ActionTranscribe and summarize eachOpenAI
  • ActionGroup summaries into themed digestOpenAI
  • ActionWrite digest page to CodaCodaCoda
  • OutputPost digest link to SlackSlack

What it does

Once a week, it collects every Loom walkthrough recorded since the last run, transcribes and summarizes each, then groups them into a themed digest page in Coda. It finishes by posting the digest link to a Slack channel so the team gets one weekly read instead of a backlog of videos.

When to use it

Use it when walkthroughs pile up and nobody watches them. A scheduled weekly rollup keeps stakeholders current with a five-minute read and a single Coda page they can search later.

How it works

  1. 1A weekly schedule triggers the flow.
  2. 2The flow lists Loom recordings created in the past week.
  3. 3For each, it fetches the transcript and asks OpenAI for a tight summary plus a theme tag.
  4. 4OpenAI groups the summaries into themed sections for the digest.
  5. 5The digest is written to a new Coda page in the rollup doc.
  6. 6The Coda page link is posted to the chosen Slack channel.

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