SUMMARIZATION

Weekly Loom demo digest from the Coda index to Slack

On a weekly schedule, this rolls up every demo added to your Coda transcript index, has OpenAI write a themed digest of what was recorded, and posts it to a Slack channel.

CategorySummarization
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule (Monday morning)
  • ActionQuery last 7 days of demos from Coda indexCodaCoda
  • LogicSkip run if no new demos this week
  • ActionCluster by theme and write digest with OpenAIOpenAI
  • OutputPost weekly digest to Slack channelSlack

What it does

Once a week it scans the Coda transcript index for demos added in the last 7 days, asks OpenAI to cluster them by topic and write a short readable digest, and drops that digest into a Slack channel with deep links to each video chapter.

When to use it

Use this when demos pile up faster than anyone reviews them. Instead of expecting the team to browse Coda, you push a curated weekly summary so everyone knows what new product walkthroughs exist and where to find them.

How it works

  1. 1A weekly schedule trigger fires every Monday morning.
  2. 2A Coda query pulls all index rows created in the last 7 days, including titles, summaries, and chapter links.
  3. 3A logic step checks whether any new demos exist; if none, the run exits quietly.
  4. 4OpenAI groups the demos by feature theme and writes a scannable digest with bullet links.
  5. 5A Slack action posts the digest to the demo-library channel so the whole team gets the weekly rollup.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect CodaDocs, packs, automations.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  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.