SUMMARIZATION

Compile the week's team Looms into a Confluence walkthrough index

Runs weekly, transcribes every team Loom recorded that week into individual step-by-step pages.

CategorySummarization
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionList Loom videos from the past 7 daysLoomLoom
  • ActionTranscribe and write up each recordingOpenAI
  • ActionCreate a Confluence child page per walkthroughConfluenceConfluence
  • OutputRebuild topic-grouped Confluence index pageConfluenceConfluence

What it does

Once a week this workflow gathers all of the team's new Loom recordings, writes each one up as a step-by-step Confluence child page with chaptered timestamps, and updates a parent index page that links to them grouped by topic.

When to use it

Your team records a steady stream of Looms and you want a maintained knowledge base rather than scattered links. Use this to keep an always-current Confluence space of written walkthroughs with zero manual curation.

How it works

  1. 1A weekly schedule kicks off the run and queries Loom for all videos created in the past seven days.
  2. 2For each video, the workflow pulls its transcript and chapter markers.
  3. 3An AI step writes each transcript into a structured walkthrough page and classifies it under a topic label.
  4. 4A Confluence child page is created per video, with chapter headings linked to their Loom timestamps.
  5. 5The workflow rebuilds the parent index page, listing the week's new walkthroughs grouped by topic with recorder and date, so the space stays organized over time.

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 ConfluenceSpaces, pages, blueprints.
  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.