Skip to content
Northstar Solutions

The first call is free.

Contact us

Implementation

Translate your HubSpot knowledge base with Phrase – how we built the connection

HubSpot's knowledge base supports languages but has no translation workflow. How we connected it to Phrase TMS and a translation agency with a custom app.

By , founder and RevOps consultant

Implementation · Support· 8 min read

A HubSpot knowledge base can be translated three ways: by hand, with machine translation, or through a connection to a translation management system (TMS). For a software company with a multilingual help centre in HubSpot, we built the third: a custom app in HubSpot that sends articles to Phrase TMS, where their translation agency works, and brings the finished translations back. The app keeps track of which translations are up to date and which need redoing, so nobody has to do it in a spreadsheet.

Why Phrase's own HubSpot connector wasn't enough

HubSpot's knowledge base supports several languages. Each article can have one language variation per language, linked to the English article. But HubSpot has no workflow for requesting translations, sending them to an agency or seeing when they are done.

Phrase has a ready-made HubSpot connector. According to Phrase's own documentation, as of November 2026, it covers website pages, landing pages, themes, blog posts, emails, forms and files. Knowledge base articles aren't included. HubSpot apps can't add cards or panels to the knowledge base editor either.

Without a connection, the work is manual. Someone exports the articles, emails files to the agency, pastes the translations back and tries to remember which languages went out of date when the English text changed. With a help centre in several languages and dozens of articles, that is hard to keep track of.

How the app works

The app has its own page in HubSpot (an app page), built on HubSpot's developer platform. It has three views.

The overview. Every English article on one row, with a coloured badge per language. Green means up to date, blue in Phrase, yellow ready to publish, red out of date or a formatting problem, and grey not requested. There are saved views such as "Needs translation" and "Ready to publish", filters by language and category, search and bulk actions.

The article page. Every language for one article, with its publish status, translation status and what has happened. Below that, the jobs in Phrase, with step, status, how far the translator has got and the due date.

Settings. Test or live mode, whether translations are published as soon as they arrive, which Phrase template is used, and checks that the connection and the knowledge base are set up correctly. Only users who can manage apps in HubSpot can change them.

How a request travels from HubSpot to Phrase and back

A translation from request to publishing

1 · HubSpot

Request

Articles and languages are picked in the app. The checks run before anything is sent.

2 · Phrase TMS

Translation

One job per language. The agency translates with the translation memory as a base.

3 · HubSpot

Check and draft

The formatting is checked. The translation is saved as a draft or published.

  1. Request. Someone in the support team picks articles and languages. With "Request changes" they can describe what should change.
  2. Checks. The app stops the request if the language isn't turned on in the knowledge base, or if the English article isn't published. It also stops it if the language is already requested. The article's category must have a name in that language, because HubSpot won't save the translation otherwise.
  3. To Phrase. All requests go to one long-running project in Phrase. Each article is sent as an HTML file with its title and body. A language with no job gets a new one. A language that already has a job gets the new English text through Phrase's Update source, so the same job is reused.
  4. A note for the translator. Phrase doesn't show a per-job note in the editor, so the app adds the note as a comment on the title segment. The translators see it where they work.
  5. Back to HubSpot. When the job is done in Phrase, the app downloads the translation and saves it as a draft, linked to the English article, in the same category. If the setting says so, it is published straight away.
  6. Publishing. Finished drafts collect in the "Ready to publish" view. One click publishes one language. A bulk action publishes every ready language for several articles and shows how far it has got.

Step 3 is what saves money. When the English article changes, the app creates no new job. It updates the source of the existing job. The translation memory carries over, and the agency only translates the sentences that changed.

The check that stops broken formatting

Phrase turns the HTML in each segment into tags. A translation must have the same tags as the English segment, or parts of the page break. A code example can show as plain text, for example. Phrase can still set the job to Completed.

So the app checks every delivery, segment by segment, before it is saved in HubSpot. If the tags differ, the translation is saved as a draft, even when publishing on arrival is turned on. The app shows a red badge with the segments to fix and a link to the job in Phrase. The red badge stays until a new delivery comes back with matching tags.

Why the app checks Phrase instead of waiting for a webhook

The obvious choice would have been for Phrase to call HubSpot when a job is done (a webhook). But in this setup, a public endpoint that Phrase could call would have needed Content Hub Enterprise, which the client didn't have. So the app checks Phrase itself: when someone opens a page in the app, and when someone clicks "Check Phrase".

That is a deliberate trade-off. A finished translation waits in Phrase until someone opens the app, but the support team uses the app every day. The app checks a few articles per call, so each call stays within HubSpot's 15-second limit for serverless functions, and the page shows how far it has got.

Two other things we solved along the way:

  • Two open tabs. If two people have the app open at once, both could try to deliver the same translation. The app marks a delivery as in progress for two minutes, so the other page leaves it alone.
  • Corrections in Phrase. A translator can correct a text in Phrase after delivery. "Check Phrase" finds those jobs and brings them in, if they differ from the draft in HubSpot.

Test first, then live

The app has a test mode with its own projects in Phrase, so the team can try the whole flow without sending work to the agency. Every new version is tested in a HubSpot sandbox account first and gets a version number and a changelog. API keys are stored as secrets in HubSpot, never in the code, and the settings page can test the connection without changing anything.

The help centre is one part of customer support in HubSpot. How tickets, SLAs and Customer Agent are set up in HubSpot is covered in Customer support in HubSpot. A knowledge base in the customer's language also gives Customer Agent better material.

More integrations we have built around HubSpot: customer requests from the company record to Linear and linking companies to their parent company automatically.

Common questions

Does HubSpot translate knowledge base articles automatically? HubSpot lets you create a language version of each article, linked to the original. How much HubSpot can translate with AI changes often, so check it in your account. If an agency should translate, or you want translation memory and control over what is up to date, you need a translation management system.

Can Phrase TMS connect to the HubSpot knowledge base? Not with Phrase's ready-made connector, as of November 2026. It covers website pages, landing pages, themes, blog posts, emails, forms and files. The knowledge base needs a custom integration with Phrase and HubSpot's APIs, like the one we built.

How do you keep translations up to date when the English article changes? Compare when the English article and the translation were last changed, and send the out-of-date languages again. In our app, the existing Phrase job is reused, so the translation memory carries over and only the changed sentences need translating.

How do you stop a translation from breaking an article's formatting? Check that every translated sentence has the same HTML tags as the original before it is saved. If a translation that differs is only saved as a draft, a broken page is never published.

Which HubSpot licence do you need for an app like this? The knowledge base is part of Service Hub Professional and Enterprise. Our app uses HubSpot serverless functions, which need an Enterprise licence. Check the requirements in HubSpot's developer documentation, since they change. Receiving a webhook from Phrase would have needed Content Hub Enterprise as well, so the app checks Phrase itself instead.

Can we move translated help articles from another help desk to HubSpot? Yes, articles and their translations can be moved with HubSpot's APIs. If you already use Phrase, the translation memory stays in Phrase and is reused for the new jobs.

About the author

Viktor Olsson, founder and RevOps consultant

Viktor has worked with HubSpot for six years, with teams from 3 people to organisations with 30 sales reps across the Nordics. He also works in RevOps at an international SaaS company.

LinkedIn →

Want to get your sales and CRM in order?

The first call with Viktor takes 30 minutes and is free. We'll go through how you work today and what would make the biggest difference.

Contact us