OTHER
Translate a release-notes draft dropped in Drive
When a Markdown release-notes draft is added to a watched Google Drive folder, translate it into all configured languages and write each localized copy back beside the original.
How it runs
The automated pipeline, trigger to output.
- TriggerNew Markdown draft in Drive folderGoogle Drive
- ActionDownload and parse draftGoogle Drive
- LogicSkip files already localized
- ActionTranslate body per target languageHugging Face
- OutputWrite localized copies to folderGoogle Drive
What it does
Watches a Google Drive folder for new release-notes drafts. As soon as a writer drops in a Markdown file, it translates the content into every language you ship and saves the localized versions next to the source so the whole set is ready for review or publishing.
When to use it
Use it when your release notes are authored by hand (PM or docs writer) and the only repetitive step is fanning the approved draft out into all your supported languages.
How it works
- 1A new `.md` file appears in the watched Drive folder (trigger).
- 2The flow downloads the file and parses headings and body, preserving Markdown structure and code blocks.
- 3A logic step skips files already containing a locale suffix to avoid re-translating outputs.
- 4A Hugging Face translation model renders the body into each target language while leaving code untouched.
- 5The flow writes one localized Markdown file per language back into the same folder, suffixed by locale code.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect Hugging FaceModels, datasets, spaces — the open-source hub.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Other workflows
Sweep stale visitor check-ins, auto-checkout, and flag overdue guests
On a recurring schedule this finds visitors still marked on-site past their expected departure, auto-checks-out anyone past end-of-day.
Pre-register a visitor, email a QR badge, and alert the host on arrival
When a host submits a visitor pre-registration form, this creates a visitor record, emails the guest a scannable QR badge with arrival instructions.
Build a daily expected-visitor roster and send it to the front desk
Every morning this pulls the day's pre-registered visitors from Airtable, builds a sorted arrival roster with hosts and times.
Agent-Driven Full IVR Re-Voicing for a Rebrand
An agent takes a rebrand brief from Notion, audits every IVR prompt for old naming, rewrites and re-synthesizes the affected ones with ElevenLabs, archives them to Dropbox.
Sync IVR Prompt Registry in Airtable to Fresh ElevenLabs Audio
Runs nightly against an Airtable IVR prompt registry, finds rows whose script text changed since last synthesis, regenerates only those ElevenLabs clips.
Slack-Approved IVR Re-Voicing After a Product Rename
On demand from Slack, drafts updated IVR prompt scripts for a renamed product, posts them for human approval.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.