DEVOPS

Audio changelog: spoken release notes in every language

On each published GitHub Release, convert the notes into natural-sounding voiceover in multiple languages and drop the audio files into a shared Google Drive folder…

CategoryDevOps
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerGitHub Release publishedGitHubGitHub
  • ActionExtract and clean narration text
  • ActionTranslate narration per localeHugging FaceHugging Face
  • ActionGenerate ElevenLabs voiceover per languageElevenLabsElevenLabs
  • OutputUpload MP3s to release Drive folderGoogle DriveGoogle Drive

What it does

Produces an audio version of your release notes. Whenever a GitHub Release is published, it translates the notes, generates lifelike voiceover for each language with ElevenLabs, and files the resulting MP3s into a per-release Google Drive folder ready for changelog pages, in-app players, or accessibility use.

When to use it

Use it when you ship audio or video changelogs, support visually-impaired users, or want a podcast-style "what's new" clip per release in the languages your customers speak.

How it works

  1. 1A GitHub Release is published (trigger).
  2. 2The flow extracts the release body and strips Markdown into clean narration text.
  3. 3A Hugging Face model translates the narration into each target language.
  4. 4ElevenLabs synthesizes a separate voiceover track per language using your chosen voice.
  5. 5The flow creates a Drive folder named for the release tag and uploads every MP3, returning the shareable folder link.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect Hugging FaceModels, datasets, spaces — the open-source hub.
  3. 3
    Connect ElevenLabsText-to-speech, voice cloning.
  4. 4
    Connect Google DriveDocs, sheets, slides, files.
  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.