> ## Documentation Index
> Fetch the complete documentation index at: https://hyperlocalise.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Localize Intercom Help Center articles

> Import Intercom articles into a native project, translate them in Jobs, and push approved drafts back to Intercom.

Use a saved automation to import Intercom Help Center articles into a native project as markdown, translate them in [Jobs](/platform/translation/jobs), then write approved translations back to Intercom as drafts. Import never publishes to Intercom. **Push to Intercom** is a separate action.

## Connect Intercom

1. Open workspace **Integrations** and find **Intercom**.
2. Complete the Intercom authorization for the workspace that owns the Help Center.
3. Confirm the connection shows as connected. Reauthorize if Platform asks you to.

The automation uses this Intercom connection. Connect Intercom before you add the **Translate Intercom Help Center articles** skill.

## Prepare the native project

Create or choose a [native project](/platform/projects/create-project) whose source locale and target locales map onto the Help Center locales. Exact tags match first. Language-only aliases such as `en` ↔ `en-US` and `de-DE` ↔ `de` are supported when only one regional form is present. Keep locked pairs separate: `en-US` is not `en-GB`, `zh-CN` is not `zh-TW`, `pt-BR` is not `pt`, and `de` is not `de-form`.

After you select a Help Center, the editor lists that Help Center’s locale codes. Use those codes on the project.

## Create the automation

1. Open workspace **Automations** and select **New Automation**.
2. Apply the **Translate Intercom Help Center articles** template, or add that skill from **Add Skill**.
3. Attach the native project.
4. Choose a **scheduled** or **manual** trigger. A schedule imports changed articles. It does not push translations.
5. Under **Intercom Help Center**, set:
   * **Intercom region** (`United States`, `European Union`, or `Australia`)
   * **Help Center**
   * **Intercom source locale** (usually the Help Center default)
   * Optional **Collection IDs** to limit import to those collections
   * **Include draft articles on import** is on by default. Uncheck it to import published articles only
   * **Existing Intercom translations**: **Only empty locales** (default), **Refresh imported locales**, or **Overwrite all locales**
   * **Overwrite Intercom drafts when remote target is newer** is on by default. Uncheck it to keep Intercom drafts that teammates edited after the last push
6. Save the automation.

Intercom is not a trigger type. Use a schedule or **Run now** for import. Use **Push to Intercom** for write-back.

## Import articles

**Run now** or wait for the schedule. Import writes one markdown source file per article at `intercom/{help-center-slug}/{article-title-slug}.md`. The file has YAML `title` and `description` frontmatter and the Intercom article body as markdown. Review those files in the project like other [Markdown sources](/platform/projects/files). In the Content Editor, source and translation show the same markdown, including links as `[text](url)`.

Without collection IDs, import includes articles in Help Center collections and standalone articles in that Help Center. With collection IDs, import includes only articles in those collections.

A later import still checks mapped target locales when the English source has not changed. If Intercom already has a title and body for a mapped locale, import can seed that copy as an approved translation. Title-only locales and empty HTML stubs are not imported. **Only empty locales** never overwrites work already in Hyperlocalise.

Import also reads locale keys on the article. A German slot still maps when the saved Help Center list omitted `de`.

When **Create native TMS job** is enabled, the run opens a job for mapped locales that still need translation. Locales just imported from Intercom, locales already push-ready, and locales already on an open job for that file are left out. An unchanged source does not block that leftover job. If **Translate with agent** is enabled, that leftover job is assigned to the agent.

Inspect **Run History** for imported, skipped, and failed articles, plus imported translations and jobs created.

Import does not write translations to Intercom.

## Review and push drafts

1. Translate and [approve](/platform/cat) every visible string for a mapped locale, including the article title.
2. In the Content editor header, choose **Ingest** to import the automation’s configured Help Center set, or **Push to Intercom** when at least one mapped locale is fully approved and no push is already running. Choose which mapped articles to write as Intercom drafts; the open file is selected by default. The dialog also shows the automation’s push policy for newer Intercom drafts. Hyperlocalise then opens the automation **Run History** tab so you can follow the run.
3. Confirm Intercom shows the new locale content as **draft**. Publish in Intercom after you review those drafts.

A later push skips a locale whose approved text already matches the last successful push, unless you enable overwrite for newer Intercom drafts.

## Change or remove access

Disconnect Intercom from **Integrations** when this workspace should stop using that Intercom account. Inspect automations that depend on the connection before you disconnect. After you reconnect, confirm the region and Help Center still match.

If a Help Center is missing, confirm the Intercom workspace, region, and that you completed authorization. See [Connection troubleshooting](/platform/help/connections).

## If import or push does not run

* Confirm Intercom is connected and the automation is **Active**.
* Confirm the Help Center and region match the Intercom workspace.
* Confirm project locales map onto the Help Center locale codes (exact tags or the supported language-only aliases). Do not pair locked writing-system or regional variants.
* If **Ingest** is missing, confirm an active Intercom automation is attached to the project and you can manage automations. Ingest stays available before any locale is push-ready.
* If **Push to Intercom** is missing, approve every visible string for at least one mapped locale (including the title), confirm you have permission to manage automations, and wait until any in-progress push finishes.
* Open **Run History** for the failed article or locale.

See [Automation troubleshooting](/platform/help/automations) and [Connection troubleshooting](/platform/help/connections).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.