CONTENT CREATION
Reassemble approved translations into a publish-ready bundle
Once every per-locale Asana task is marked approved, collects each locale's translated file from Google Drive, reassembles them into a single localized bundle.
How it runs
The automated pipeline, trigger to output.
- TriggerAsana task marked approvedAsana
- LogicCheck whether all sibling locale tasks are approved
- ActionRead each approved locale file from Google DriveGoogle Drive
- ActionWrite combined per-locale bundle to publish folderGoogle Drive
- OutputAnnounce completed bundle in SlackSlack
What it does
Closes the loop on a split localization job. When the last outstanding locale task is approved, it gathers every translated file, assembles them into one structured bundle keyed by locale, and signals that the content is ready to ship.
When to use it
Use it when translations are produced in parallel and you only want to publish once all languages clear review. It prevents partial releases where some locales go live before others are approved.
How it works
- 1An Asana event fires when a localization task changes status to approved.
- 2A logic step checks whether all sibling locale tasks under the same parent are now approved; if any remain open, it stops.
- 3When the set is complete, a Google Drive action reads each locale's approved file from the request folder.
- 4A second action writes a combined bundle file (one section per locale) back to a publish-ready Drive folder.
- 5A Slack output announces the completed bundle with a link and the locale list.
Set it up
What you configure once, before turning it on.
- 1Connect AsanaTasks, projects, milestones — everywhere.
- 2Connect Google DriveDocs, sheets, slides, 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.