SUMMARIZATION

Loom Standup Transcript Archive to Drive and Confluence

Transcribes each new standup Loom, saves the full transcript to Google Drive, and publishes a structured summary with owners and blockers to a running Confluence log page.

CategorySummarization
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew Loom standup uploadedLoomLoom
  • ActionRetrieve full transcript from LoomLoomLoom
  • ActionSave verbatim transcript to Google DriveGoogle DriveGoogle Drive
  • ActionSummarize into decisions, owners, blockersHugging FaceHugging Face
  • OutputAppend dated entry to Confluence standup logConfluenceConfluence

What it does

This workflow builds a durable, searchable record of every standup. On each new Loom upload it stores the verbatim transcript as a file in Google Drive for compliance and search, then appends a clean structured summary, owners, decisions, and blockers, to a rolling Confluence standup log.

When to use it

Use it when standups need to be retrievable months later: onboarding new hires, settling "who decided what," or audit trails. Drive holds the raw record; Confluence holds the readable history.

How it works

  1. 1A new Loom standup upload triggers the run.
  2. 2Loom returns the full transcript.
  3. 3The verbatim transcript is saved as a dated file in the standup folder in Google Drive.
  4. 4A Hugging Face model produces a structured summary with decisions, owners, and blockers.
  5. 5The summary is appended as a dated entry to the running Confluence standup log page.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect LoomVideo transcripts, libraries.
  2. 2
    Connect Hugging FaceModels, datasets, spaces — the open-source hub.
  3. 3
    Connect Google DriveDocs, sheets, slides, files.
  4. 4
    Connect ConfluenceSpaces, pages, blueprints.
  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.