CONTENT CREATION

Turn a new source doc into a localization brief and tasks

When a new source document lands in a watched Google Drive folder, extracts the copy, uses OpenAI to draft a localization brief (tone, glossary, locale notes), and opens…

CategoryContent Creation
EngineSim + Paperclip
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew source document added to Drive folderGoogle DriveGoogle Drive
  • ActionRead the source document textGoogle DriveGoogle Drive
  • ActionDraft localization brief and resolve target locales with OpenAIOpenAI
  • LogicExpand locale list into per-locale work items
  • OutputCreate per-locale Asana tasks pre-loaded with the briefAsanaAsana

What it does

Makes filing into a Drive folder the entire request action. It detects a new source document, pulls its text, generates a structured localization brief covering tone, key terms, and locale-specific cautions, then spins up the per-locale tasks already carrying that context.

When to use it

Use it when content authors finalize copy in Drive and you want localization to begin automatically — no separate form or ticket. Best when target locales are consistent per folder or encoded in the document.

How it works

  1. 1A Google Drive trigger fires when a new file appears in the watched source folder.
  2. 2A Google Drive action reads the document's text content.
  3. 3An OpenAI action drafts a localization brief: tone summary, glossary candidates, and per-locale notes, plus the resolved target-locale list.
  4. 4A logic step expands the locale list into work items.
  5. 5An Asana action creates one task per locale, each pre-filled with the source copy and the generated brief.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect AsanaTasks, projects, milestones — everywhere.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.