CONTENT CREATION

Segment a dropped Google Drive doc into a per-string translation sheet

When a doc lands in a watched Drive folder, segment its sentences into rows of a new translation tracking sheet with source, target, and status columns.

CategoryContent Creation
Enginesim
Difficultybeginner
Triggerevent
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew document added to watched Drive folderGoogle DriveGoogle Drive
  • ActionDownload file and extract textGoogle DriveGoogle Drive
  • LogicSegment into sentences, skip boilerplate
  • ActionCreate sheet with one row per segmentGoogle DriveGoogle Drive
  • OutputShare sheet and link it in #localizationSlack

What it does

Converts a free-form source document into a structured translation workbook. It reads the dropped file, splits the text into sentence-level segments, and writes each segment as a row in a fresh Google Sheet with empty Target and Status columns ready for a linguist to fill in.

When to use it

Use it when marketing or legal copy arrives as a Drive document rather than structured content. Sentence segmentation gives translators consistent units and lets reviewers track progress row by row instead of editing prose blindly.

How it works

  1. 1A new file created in the watched Drive folder fires the trigger.
  2. 2The flow downloads the document and extracts its plain text.
  3. 3It segments the text into sentences, skipping headers, URLs, and boilerplate lines.
  4. 4It creates a new Google Sheet and writes one row per segment with Source, Target, Status=Pending, and segment index.
  5. 5The sheet is shared with the linguist group and a Slack note links it in #localization.

Set it up

What you configure once, before turning it on.

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