The wxrks Pendo connector pulls in-app guide content out of a Pendo subscription and creates a wxrks translation project from it. Once translation is finished, wxrks delivers the localized guide content back into the same Pendo instance automatically.
💡 Who is this for? This guide is for Account Admins (or anyone your account has granted connector configuration access) who set up and maintain the Pendo connector. If you don't see Integrations in the sidebar, ask your account admin to grant connector access.
Key concepts
Term | What it means |
Configuration | A saved connection between wxrks and one Pendo subscription, tied to a specific wxrks Organizational Unit. You can create more than one. |
Guide | A Pendo in-app guide, identified by its Guide ID. You choose which guides to translate by listing their IDs when you sync. |
Sync (Create Project) | The action that pulls the content of the guides you list out of Pendo and creates a wxrks translation project from it. A sync is triggered on demand from a configuration, not automatically. |
CI Tag | A label that groups related syncs into the same wxrks project. Pendo defaults this to |
Locale copies | An optional setting on the configuration that automatically re-delivers a finished translation to one or more extra locale codes, with no separate translation pass. Covered in Step 1 below. |
Before you start
Have the following ready:
A Pendo API key with access to the guides you want to translate, and your Pendo subscription's API base URL (check Pendo's own documentation for the correct host for your account/region — see Good to know below for why this matters).
The wxrks Organizational Unit that should own the translation projects created from Pendo. If you haven't created one yet, see How to create an Organization or Organizational Unit.
The Guide ID(s) of the guide(s) you want to translate, from Pendo's own guide list — up to 15 per sync request.
Connector configuration access in wxrks (see "Who this is for").
Step 1: Create a Pendo configuration
In the sidebar, select Integrations, then open the Pendo connector.
Switch to the Config tab and select Add Configuration.
Fill in the fields:
Field | What to enter |
Organizational Unit | The wxrks org unit that should own projects created from this configuration. |
Name | A reference name so you can recognize this configuration later. |
Workflows | The workflow(s) used by projects created from this configuration. wxrks requires at least one to be selected before you can save. |
URL | Your Pendo subscription's API base URL. See Good to know below — don't leave the pre-filled placeholder in place. |
API Key | A Pendo API key with access to the guides you want to translate. It's encrypted before it's stored. |
Params | A JSON object for optional settings. Enter |
Select Create to save the configuration.
Automatically copying a translation to extra locale codes (optional)
Sometimes the exact same translated content needs to be published under more than one locale code — for example, a single Spanish translation reused for both es and es-419. Instead of running a separate translation for each variant, the configuration's Params field supports a locales map: for a given target language, list any additional locale codes (copies) that should automatically receive the identical translated content the moment the real translation is delivered.
{ "locales": { "es": { "copies": ["es-419", "es-MX"] } }}With this configured, delivering a translation to es also immediately re-delivers that same content — with only the locale code itself changed — to es-419 and es-MX, with no extra translation work for those variants.
Step 2: Create a translation project (sync)
From the Config tab, open a configuration's row menu (⋮) and select Create Project (Sync).
Fill in the sync form:
Field | What to enter |
Organizational Unit | Fixed to the configuration's org unit — not editable from this form. |
Contact Person | Receives project notifications. Required. |
Project Reference | The new project's name in wxrks. Required. |
Source Language | Optional — falls back to the Organizational Unit's default source language if left blank. |
Target Languages | Optional — falls back to the Organizational Unit's default target languages if left blank. |
Workflows | Workflow(s) applied to every guide in this sync. If left empty, wxrks applies the Translation workflow only. |
CI Tag | Groups this sync into a project. Defaults to |
Guide IDs | A comma-separated list of Pendo Guide IDs to pull in. Up to 15 per sync request — this is Pendo's own API limit, not just a wxrks form rule. |
Skip Status Check | By default, a sync only pulls in guide/target-language pairs that are new or previously failed — anything already delivered or in progress is left alone. Check this to force every listed guide/target-language pair into this sync regardless of its current status. |
Skip Hash Check | Shown on the form, but doesn't change today's sync behavior beyond what Skip Status Check already controls above. |
Select Sync to start the project.
How delivery works
Once a synced guide's translation finishes in wxrks, the connector delivers the localized version back into the same Pendo instance automatically through Pendo's own bulk import API — there's nothing to export or re-upload by hand. If a delivery fails, the entry's status is set to Error with the reason recorded, and a later sync with Skip Status Check checked will send it again.
Managing your configurations and tracking status
The Entries tab on the Pendo connector page lists every guide/target-language pair that's been synced, with its current status. Use the filters (filename, target language, status, tag, project UUID) to narrow a long list down.
Good to know
Limits per sync: up to 15 Guide IDs, matching Pendo's own bulk export/import API limit.
Check the URL field before saving a configuration: the create-configuration screen pre-fills URL with a placeholder value and its own helper text says this field "will be auto-generated by the user credentials and doesn't need to be provided." In practice, this URL is exactly what every export and import call to Pendo is built from — replace the placeholder with your account's real Pendo API base URL rather than leaving it as shown.
Default workflow on sync: if you leave Workflows empty when starting a sync, wxrks applies the Translation workflow only to every guide in that request.
Multiple Pendo accounts: create a separate configuration for each Pendo subscription you need to pull guides from.
Combining syncs into one project: Pendo syncs default to the same CI tag (
pendo), so repeated syncs against the same Organizational Unit and source language combine into one project automatically — see How to Combine Connector Projects for the full rules.
Troubleshooting
Symptom | Likely cause and fix |
Sync fails with a "Missing Pendo project request param" error. | A required field is missing — check Contact Person, Guide IDs, Source Language, and Target Languages first. |
Sync fails with an error about too many guide IDs. | Pendo's own bulk API caps a single request at 15 guides — split the guide list across more than one sync. |
A previously-synced guide doesn't come through on a resync. | Check Skip Status Check — by default only NEW/ERROR entries are resent; check the box to force a resend. |
Quick reference
Task | Where |
Add or edit a configuration | Sidebar > Integrations > Pendo > Config tab |
Sync guides into a project | Config row menu (⋮) > Create Project (Sync) |
Check sync/translation status per guide | Pendo connector > Entries tab |
Automatically copy a translation to extra locale codes | Configuration's Params field ( |
Related articles
Using the wxrks Connectors Interface — the connector UI chrome (entries, statuses, filters) shared across all connectors.
How to Combine Connector Projects — how CI tags decide whether a new sync joins an existing project.