HubSpot: configuring access from XTM Connect – HubSpot (Locale)
To enable XTM Connect – HubSpot (Locale) to connect to your organization’s HubSpot CMS instance, it is first necessary to grant XTM Connect – HubSpot (Locale) physical access to HubSpot. This physical access :
only needs to be configured once, because it applies for your organization’s entire HubSpot CMS instance.
is a prerequisite for defining authorizations (connections) to individual HubSpot content types, which are specific parts of the HubSpot CMS. An organization can configure many content types, if required.
There can be many content type connections, which are private or shared. For details, see Securing connections to XTM Connect – HubSpot (Locale)
How is physical access arranged?
Physical access from your organization’s XTM Connect – HubSpot (Locale) instance to its HubSpot CMS instance is created using a HubSpot Private App, which you configure in HubSpot (not XTM Connect – HubSpot (Locale)). When you configure the Private App for XTM Connect – HubSpot (Locale), an access token is generated. This access token is unique to the specific Private App.
When Project managers create projects for Hubspot content, using XTM Connect – HubSpot (Locale), they enter the access token in the Authentication screen, to specify the HubSpot CMS instance from which XTM Connect – HubSpot (Locale) is to fetch content for translation, via HubSpot's APIs.
For more information, see this article about HubSpot Private Apps.
Note
Prerequisite for Private App creation
You must have a HubSpot super admin user role to create, access and manage Private Apps in your organization’s HubSpot account.
If you do not already have the super admin access credentials to log in to your organization’s HubSpot instance, ask your HubSpot system administrator or HubSpot representative to provide them. You cannot request them from XTM International Support.
Log in to your organization’s HubSpot instance as a HubSpot super admin user.
Select the Settings icon at the top of the page, on the right. A list of settings is displayed on the left of the Settings screen.
Select the Integrations > Private Apps option. The Private Apps screen is displayed.
In the top right-hand corner of the screen, select the Create a private application button. You see the Basic Info tab screen.
In the Name text field, enter a unique name for your new Private App.
Example: XTM Connect – HubSpot 12345.
Generating a random name
Instead of entering a specific name, you can, if required, generate a random name. To do so, select the Generate a new random name button, which is located under the Name text field. The generated name is inserted in the Name field.
In the Description text field, enter a description for your new Private App, to help you and other users identify the Private App in the future.
Example: "This is the Private App used by XTM Connect – HubSpot (Locale) to automatically send translation content from HubSpot to XTM Cloud and receive it back after translation and completion."
Scope settings: to specify which HubSpot scope (content types) are to be handled by the XTM Connect – HubSpot (Locale) Private App, select the Scopes tab in the center of the screen, at the top. You see the Scopes tab screen.
Select the Add new scope button.
In the Add new scope popup, enter the word "content" in the search field.
When Content is listed below the search field, select the checkbox to the right of the Content entry to enable this option. You return to the Scopes tab screen, where the Content scope is now listed.
In the top right-hand corner of the Scopes tab screen, select the Create app button. The Create a new private app popup is displayed.
To create the new Private App and generate an access token for it, select the Continue creating button. In a different popup, the creation of your new Private App is confirmed: it is listed there, with the name defined in step 6. The unique access token that has been generated for your Private App is also listed. The access token is initially displayed with # characters to hide some of its individual characters, for security purposes.
If required, you can now copy the unique access token. To do so, select the Show token button on the right-hand side of the popup. The # characters that are hiding some of the access token from view are replaced by the token’s actual alphanumeric characters.
Now select the Copy button under the Show token button on the right-hand side of the popup. The access token is copied to the Clipboard on your computer.
You can now share the access token with the appropriate people, in accordance with your organization's procedures. Project managers will use it (in the Authentication screen) when they create projects for Hubspot content, using XTM Connect – HubSpot (Locale).
Note
Security recommendation
You must store the access token somewhere secure: anyone who has the access token can use it to access, use, edit or delete your new Private App. It is essential to prevent unauthorized users from accessing the Private App.
Other connection arrangements when physical access has been set up
Once physical access from XTM Connect – HubSpot (Locale) to HubSpot has been set up, connections from XTM Connect – HubSpot (Locale) to the different types of required data on the HubSpot instance are also required. These types of required data are called content types. The connections involved are called authorizations. For details, see Authentications: connecting your HubSpot instance to the XTM Connect (Locale) platform.