spec sheet · docs & support

Help Scout and Transglot, bring your help articles into translation.

Choose Help Scout in your project’s CMS settings, add your credentials, and select the content and languages to sync. Translate and review in one project, then publish to your mapped target languages.

Import into Transglot

Direction: Import into Transglot
Plan: Starter and up
Scope: Docs articles: name and text, across your collections
Authentication: a Help Scout Docs API key
Get started: Connect from your project’s CMS settings.

Create your project Setup

docs & support

the workflow

Connect your content. Review every language.

Connect once, choose your content and languages, then translate and review in the same project. The steps below show how it works in your tool.

Connect Help Scout
Choose Help Scout in the project’s CMS settings. Add a Help Scout Docs API key.
connect
Choose the content and locale mapping
Select the types and fields you want to localize. The connector reads Docs articles: name and text, across your collections. Map the source and target locales to your project.
map
Sync and review the translations
Start Sync from CMS to bring the selected source into your project. Translate and review the resulting keys alongside the rest of your project content.
review
Deliver through your project
Pull the translated locale files through the API or CLI, or use the project’s CDN bundle. Help Scout remains an import-only source.
deliver

Read translated locale files through the Transglot API, CLI or CDN. Publishing changes back to Help Scout is not part of this connector.

what moves

What you can translate and deliver.

Docs collections and their articles come in with the full body, since the list endpoint returns only references. It stays one way because Help Scout Docs models each language as a separate site rather than a translation of an article, so there is no per article slot to publish into.

What you can translate and deliver.
Surface	What to expect
Source and scope	Docs articles: name and text, across your collections
Translated output	Read translated locale files through the Transglot API, CLI or CDN. Publishing changes back to Help Scout is not part of this connector.
Keep in mind	Import only. Your original Help Scout content is read, and this connector does not write translations back.

get connected

A few steps to your first connection.

Follow your tool’s setup below: add the connection, choose what to sync, and try it with a small set of content. Your team can keep working in the tools they already use.

What you need

a Help Scout Docs API key.

A Transglot project with its source and target locales configured.
Save credentials in the connection settings so your team can work without copying secrets between files.
Hosted API access requires a paid Transglot plan. AI translation uses your workspace’s word allowance.

Create your project

Create a Transglot project with the source and target locales you need.
Open the project’s CMS settings and choose Help Scout.
Provide a Help Scout Docs API key.
Save the connection, select the supported content, map locales, then run Sync from CMS.

same project, more possibilities