If I understand it correctly, n8n would fit best as the backend orchestration layer here, while the translation work itself could be handled through a dedicated UI such as Weblate or Crowdin, or even a custom frontend that talks to n8n through webhook/API calls.
That approach would keep the translation process safer and easier to use, especially if you want people to review strings without editing JSON directly.
I also explored a similar frontend + n8n pattern in my own Chrome extension / translator work, so I think this direction makes sense.
