Zendesk Help Center

Translate Help Center categories, sections, and articles into their existing language versions, with manual control over sync and publication.

Translate Help Center content without moving it out of Zendesk. The Lingo.dev connection reads selected categories, sections, and articles in the Help Center's default language, translates them through a localization engine, and writes target-language versions onto those same items.

In the Studio 2.5 navigation, open Studio 2.5 → Integrations instead of Settings → Integrations. Existing connection and setup links still work.

Runs are manual. After an article changes, start Sync for the content you want to update. Before the first write, choose whether translations should be drafts or live: writing an already-published target as a draft can remove that language version from readers until it is republished.

Prepare access and Help Center languages #

Zendesk Help Center integration comes with the Enterprise plan. See pricing for current availability. Settings → Integrations shows Not on your plan beside Zendesk when the organization needs plan access.

Use a Zendesk administrator account with access to Help Center content. Administrator access is required to register the article-published webhook that collects activity for Radar. Writes are attributed to the authorizing account, so use an appropriate service account if the team needs shared attribution. In Lingo.dev, you need permission and connection entitlement for the organization, plus access to the selected localization engine.

Enable the target languages in the Help Center's language settings. Zendesk's account-wide localization list is separate and does not enable Help Center translations. With appropriate authorization, the read-only endpoint https://<subdomain>.zendesk.com/api/v2/help_center/locales.json lists the Help Center locale configuration.

Lingo.dev reads the Help Center's default language on each run and uses it as the source. You do not select a different source language in the connection form.

Connect and translate a first article #

  1. Open Settings → Integrations and select Connect for Zendesk. Enter a name and the Help Center subdomain. For acme.zendesk.com, enter acme.
  2. Continue to Zendesk and authorize access. The connection is created only after authorization succeeds.
  3. In Studio, select the Help Center under Connected, then select Set up.
  4. Choose a localization engine and writeback mode, then select Continue. For this first run, select one target language from those enabled in the Help Center. The source is excluded; if no other language is available, enable one in Zendesk first.
  5. Open Articles and enable the Sync switch for one article with stable source text. Wait for the setting to save, select that article's row checkbox, and choose Queue sync.
  6. Inspect the workflow result and the actual target article in Zendesk. Check its title, body, links, locale, and draft/live state. If it should be published, open its reader-facing URL as well.

First Sync adopts complete existing translations without writing over them, preserving both text and draft state. It translates missing content. Use Retranslate when you deliberately want to replace an existing translation.

Select the whole area you want to translate #

Categories, sections, and articles have separate tables and persistent Sync switches. Enabling a category translates that category's name and description; it does not enable its sections or articles. Select those separately when preparing a complete Help Center area.

ItemTranslated fields
CategoryName/title and description
SectionName/title and description
ArticleTitle and body

Row checkboxes narrow one-off Queue sync or Queue retranslation work to items whose Sync switches are already enabled. Checking a row does not enable its persistent switch. Header actions cover the enabled connection scope. Check which selection the action will process before starting it.

Article bodies use HTML processing to reconstruct formatting, links, and embedded media. Writeback can adapt recognized Help Center links to the target locale. Inspect those links in the result, including whether the translated destination exists. External links and site-specific navigation still need their own checks.

This connection does not translate tickets, macros, themes, community posts, or articles based on Zendesk content blocks. It localizes Help Center content; it is not a support-ticket triage connection.

Update changed content or replace it #

Sync compares the current source with recorded state and existing translations. Use it for routine source updates, missing content, and incomplete work from an earlier run.

Retranslate regenerates the selected items and languages even when source text has not changed. It can replace accepted human edits. The broad header action asks for confirmation; selected-row actions still require you to choose the intended replacement scope.

One run is active per connection. Additional requests queue, and a full queue requires waiting for capacity. Workflow runs shows the outcomes; Stop cancels work that can still be stopped. An up-to-date outcome means no selected change needed processing, rather than a new assessment of the translation's quality.

Verify what readers can see #

Publish mode writes live translations. Draft mode writes unpublished locale versions for review in Zendesk. When refreshing an existing published language in Draft mode, the new draft can remove that live version until someone republishes it. Decide whether that interruption fits the release before starting the update.

After the write, inspect the target URL in the intended language. Compare the actual title and body with the source revision, follow links, and look for source-language fragments. A completed translation run is one part of the release; acceptance and publication remain editorial decisions.

Recover source changes and partial results #

Writeback rereads the source item. If it changed or was removed after planning, Lingo.dev skips the target. Run another manual Sync after the source is ready to reconcile the new state.

A failure for one locale does not undo successful writes elsewhere. Inspect written, skipped, and failed items, then retry the affected scope. Forcing the whole Help Center can replace text that was already accepted without repairing the original cause.

If output is missing, check item selection, enabled Help Center languages, access to the localization engine, writeback mode, content-block exclusions, and whether the source changed. Adopting an existing complete translation intentionally produces no new text. If a target language was disabled in Zendesk, runs skip it; refresh the connection's target selection.

For temporary Zendesk outages, retry after the service recovers. Use Reconnect on the existing connection if authorization needs restoring; disconnecting and creating a new connection discards sync state.

Disconnect or reconnect #

Change target languages, localization engine, and mode on the Help Center's Settings tab in Studio. Rename or reconnect the account in Settings → Integrations. Use Reconnect to restore authorization on the existing connection.

Disconnecting stops reads and writes and removes the local connection, run history, and per-item sync record. Existing Zendesk translations remain. Creating a new connection afterward establishes a new baseline: its first Sync retains complete translations already present and fills missing content. Revoke provider authorization separately when access should end. Restore earlier published wording directly in Zendesk when needed.

Collect activity in Radar #

The connection also supplies Help Center activity to Radar. Collect translations for measurement describes the event setup and how to import provider history before running a historical measurement.

If manual translation works but new article activity is missing, check the connection's webhook registration and delivery. Authorization can succeed even when a non-administrator account cannot register the webhook. In Settings → Integrations, use Reconnect on the existing Zendesk connection and authorize as an administrator. Publish a test article and verify its event in Radar before relying on automatic collection.