SUMMARIZATION

On-demand Loom transcription into Coda from a Slack request

When someone posts a Loom link in Slack with a command, it transcribes that specific video, summarizes it into a spec entry, adds it to the Coda rollup.

CategorySummarization
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerSlack message with Loom linkSlack
  • ActionParse link and fetch Loom transcriptLoomLoom
  • ActionSummarize into spec schemaOpenAI
  • ActionAppend row to Coda spec rollupCodaCoda
  • OutputReply in Slack thread with row linkSlack

What it does

Lets anyone trigger transcription on demand by dropping a Loom link in Slack. The flow grabs that one video, transcribes it, summarizes it into a structured spec entry, files it in the Coda rollup, and replies in the same Slack thread with a link to the new row.

When to use it

Use it when you only want certain walkthroughs rolled up, not every recording. Lets the team pull a video into the spec doc the moment it matters, straight from chat, without leaving Slack.

How it works

  1. 1A Slack message containing a Loom link and the trigger command fires the flow.
  2. 2The Loom video ID is parsed from the link and its transcript is fetched.
  3. 3OpenAI summarizes the transcript into the spec schema: summary, decisions, follow-ups.
  4. 4A new row is appended to the Coda spec rollup with the Loom URL.
  5. 5The flow replies in the original Slack thread with the Coda row link.

Set it up

What you configure once, before turning it on.

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