This workflow is designed to assist with localization
Note I haven't bulletproofed or scaled mine heavily, but I was structuring it for that goal ( large jobs, multiple agents, API rate limits, dictionaries, automated, triggered by base locale updates, even smart to manual locale-specific changes ).
Key thing is I avoided CSV because of the automation requirement- but the Webflow CLI has been developing as well and worth looking at, it may have added some things.
Structurally it helps me to think of it as 3 separate subsystems-
- Worklisting -
- determines a chunk of remaining work to do, e.g. 100 blog articles.
- tracks what was completed, and when ( and often by which workflow version )
- Translation - Do the work, and write the translated content back
- Verification
- Use a different agent, compare two published pages. You'll pick up
A few tips-
- design and test your workflow against a clone of the site.
- use the batch mode APIs to minimize API thrashing and rate limit issues
- use large context windows in the translation step, I use Opus 4.8 for most everything. I believe Sonnet also has a 1 mil context window now.
- for worklisting, I'm adding 2 fields to the collection I'm translating- the last translated date, and the script version that did the translation. that way if I find an unwanted glitch in verification, like "oh it's translating the company name", I can just fix and rerun, and worklist is already tracking everything
- it's not sexy, but if you have a lot of items in your collection e.g. between 1000 and 2000, you can create a hidden worklist page on your site. 20 collections, each ranged, it makes it easy for the agent to retrieve the open work quickly in one HTTP GET.
- don't just throw agents at it, a lot of of the work here is deterministic. lean into python scripts etc as part of the process esp the worklisting phase
- ideally, do a full backup of your data first. CSV would be ideal here, but automating it may be tricky- check the CLI in case it supports that now. If not, write a python script to iterate through the batch endpoints and export your own file backup
