CONTENT CREATION
Stage a Drive master file into per-locale subfolders with glossary copy
Watches a Drive intake folder and, for each master doc dropped in, creates a per-locale subfolder containing a copy of the source plus a generated glossary sheet.
How it runs
The automated pipeline, trigger to output.
- TriggerNew master file in Drive intake folderGoogle Drive
- LogicValidate file type and locale list
- ActionExtract and translate glossary terms per localeOpenAI
- ActionCreate per-locale subfolder and copy sourceGoogle Drive
- OutputPost subfolder links to localization leadSlack
What it does
Builds a ready-to-translate folder structure in Google Drive. When a master document lands in the intake folder, it spins up a subfolder per target locale, drops in a copy of the source file, and adds a glossary doc so each translator works from a self-contained packet.
When to use it
Use this when your translators work directly in shared Drive folders rather than a ticketing tool, and you want every locale to get an identical, isolated copy of the source with its glossary attached.
How it works
- 1A new file appearing in the Drive "Localization intake" folder triggers the run.
- 2The flow reads the file's locale list from a naming convention or a companion sheet.
- 3A check confirms the file type is supported and at least one locale is named; unsupported files are moved to a review folder.
- 4OpenAI extracts candidate glossary terms from the source and proposes translations per locale.
- 5For each locale, the flow creates a subfolder, copies the source file into it, and writes a glossary doc.
- 6A final notice lists the new subfolder links so the localization lead can assign translators.
Set it up
What you configure once, before turning it on.
- 1Connect Google DriveDocs, sheets, slides, files.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Content Creation workflows
Build a Dropbox B-roll library from exported blog drafts
Triggers when a new blog draft file lands in a Dropbox folder, generates a Replicate B-roll clip for each paragraph.
Generate B-roll clips when a blog post is marked Ready in Notion
Watches a Notion blog database for posts flipped to 'Ready', splits the body into paragraphs, and generates a short B-roll video clip for each paragraph with Replicate.
On-demand: turn a blog URL into narrated B-roll clips
Accepts a blog URL via webhook, scrapes the article, generates a B-roll clip per paragraph with Replicate and a voiceover with ElevenLabs.
On-Demand Screenshot Freshness Report from a Slack Command
A writer requests a freshness check in Slack for a specific docs page; the workflow inspects every screenshot on that page, scores each by age and version gap.
Sync a Figma master frame into localized hero renders
Pulls the current master hero frame and its text layers from Figma, generates a localized image variant for each locale defined in Airtable.
Research-driven localized hero banners tuned per market
An agent researches cultural and seasonal cues for each target market, adapts the master hero concept to fit local context, generates a tailored image per locale.
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.