Content platforms

Connect HubSpot

Import HubSpot blog post titles and bodies into transglot for translation.

Import only

Nothing is written back to HubSpot today: its per-language write path (creating a language variation of a published post, then editing it) is not supported yet. Take the translations out through the REST API, the transglot CLI or the CDN.

DirectionImport only
ImportedThe htmlTitle and postBody of source blog posts
Written backNothing
SyncSync from CMS
PlanStarter and above

Before you start

Create a private app in your HubSpot integration settings with the content scope, and copy its access token.

Connect

Open your project's settings, choose CMS, and pick HubSpot in the CMS list. There is no URL to type: the token identifies your HubSpot account.

FieldWhat to enter
Private app tokenThe private app's access token (it starts with pat-)
Content typesblog-posts
Translatable fieldshtmlTitle, postBody, or both

Select Connect, then Test connection. The test reads one blog post.

What gets imported

transglot reads your blog posts through the CMS Blogs API and imports each post's title and body. A post that is already a translation of another post (a language variation) is skipped, so a translation is never imported as source text.

Troubleshooting

  • ... the credentials were rejected. The token is wrong, revoked, or the private app does not have the content scope.
  • ... the blog or post was not found. The post was removed while the sync ran. Run Sync from CMS again.
  • ... HubSpot is rate-limiting the request, retry. Wait and run the sync again.

On this page