CONTENT CREATION

Weekly Audit of Missing Subtitle Languages with Slack Report

Runs every Monday, compares each course video in R2 against your required language list, and posts a Slack report of every lesson still missing subtitle or dub coverage.

CategoryContent Creation
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly Monday schedule
  • ActionList lesson files under R2 lessons prefixCloudflareCloudflare R2
  • LogicCompute missing languages per lesson
  • LogicBranch on full coverage vs gaps
  • OutputPost coverage-gap report to SlackSlack

What it does

This scheduled audit checks your localization completeness. It lists every course video stored in R2, cross-references the subtitle and dub files present for each, and flags any lesson that is missing one or more required languages, then posts a prioritized gap report to Slack.

When to use it

Use it to keep a large back-catalog honest. When dozens of lessons should each have five language tracks, manual tracking breaks down. This gives the content ops lead a single weekly list of exactly what to localize next.

How it works

  1. 1A Monday-morning schedule fires the trigger.
  2. 2List all lesson objects under the R2 `lessons/` prefix and group files by lesson ID.
  3. 3For each lesson, compute which required languages have a complete subtitle plus dub pair versus which are missing.
  4. 4Branch: if every lesson is fully covered, post a short all-clear and stop.
  5. 5Otherwise, build a table of incomplete lessons sorted by how many languages they lack.
  6. 6Post the coverage-gap report to the localization Slack channel.

Set it up

What you configure once, before turning it on.

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