Skip to main content

​
The HubSpot connection

A HubSpot connection links your organization’s Card Studio to a real portal. It gives the designer portal-specific field labels and options, and lets the runtime tie signed requests to the right organization.

​
Connect the portal

If the server is configured for HubSpot OAuth and the organization does not yet have a portal, Connect HubSpot appears on the dashboard.
  1. Choose Connect HubSpot.
  2. Log in to HubSpot if prompted.
  3. Choose the portal to connect.
  4. Review the requested scopes and approve.
  5. You are sent back to Card Studio.
The dashboard then shows Portal [id] connected. In the current product version, any logged-in Card Studio user can start the install flow. The organization should still agree that an owner or a HubSpot Super Admin performs the connection.

​
What the connection is used for

  • real property labels on standard and custom objects;
  • the portal’s enumeration options for importing into input fields;
  • CRM reads and writes with the approved scopes;
  • a secure link between a HubSpot portal and a Card Studio organization;
  • automatic token renewal on the server.
Tokens are never sent to the browser and are stored encrypted on the server.

​
Limitations

A HubSpot portal can only be linked to one Card Studio organization. An attempt to connect it to a different organization is rejected. The connection does not automatically make every user action allowed. The current HubSpot user’s permissions and the app’s scopes still affect what can be viewed and written.

​
If the button is missing

  • If a portal ID chip is shown, the organization is already connected.
  • If neither the button nor the chip is shown, OAuth is probably not configured on the server.
  • If the installation is rejected, check that you are allowed to install apps in the selected HubSpot portal.

​
If fields are still missing

Reopen the card so field metadata is fetched again. Use the field picker’s advanced internal name as a temporary workaround. Also check that the card’s object matches the object the field belongs to.