HubSpot is listed in the Data Sources tab on https://lengrowth.com/integrations. As with every company-linked source in LenGrowth, you need to choose a company workspace before the connection can be attached. If no company has been created yet, the integrations page tells you to create one first. That is a real UI rule, not just a documentation preference, and it applies to HubSpot the same way it applies to the analytics and ads connectors.

The backend usage metadata describes HubSpot as pipeline, lead quality, and deal progress signals. It says the source is used in founder reporting commercial sections and in existing roadmap and task creation for pipeline health. In other words, LenGrowth uses HubSpot as a commercial signal source, not as a full CRM replacement. The app reads HubSpot so it can reason about pipeline health and commercial progress inside the same reporting and task flow that the rest of the product already uses.

HubSpot is one of the integrations that uses a manual token field rather than a browser OAuth popup. On the integrations page, the connect form includes a field labeled Private app token. That label is important because it tells the user exactly what LenGrowth expects. The frontend API call posts a company ID and an access token to the /integrations/hubspot/connect route. The connection flow is therefore token-based and company-specific.

Before starting, the backend guidance says to use a HubSpot admin seat that can create and view private apps. It also says to confirm which portal the company wants LenGrowth to read before generating the token. That is a crucial detail because a private app token is only useful for the HubSpot portal it was created in. If the wrong portal is used, LenGrowth may connect successfully but the data will not belong to the business the user intended.

The backend guidance tells the user where to find the token: open HubSpot Settings, then Integrations, then Private Apps. From there, create or open the app used for LenGrowth and copy the private app token from that screen. This is not a general “connect your account” workflow. It is a very specific credential-copy step. The app expects a live token with the right scopes and enough access to the portal’s commercial data.

Once connected, the card shows the selected source, which can be the account name or account ID if one is available. The integration metadata says the connection unlocks commercial reporting and helps pipeline-health tasks move out of a waiting state when LenGrowth can fetch live CRM inputs. That makes HubSpot valuable when a company’s growth process depends on knowing what is happening with leads, deals, or the sales pipeline.

The route pattern in the frontend API is simple: /integrations/hubspot/connect for setup, /integrations/hubspot for connection state, and the same base route for disconnect. The page also uses the same company selection rule as the rest of the integrations page. That means the source is attached to a company profile and can be replaced later if the team changes which HubSpot portal it wants to read.

If setup fails, the backend guidance suggests regenerating the private app token and reconnecting with one that still has the needed scopes. It also says to confirm that you are in the correct HubSpot portal and that private apps are allowed for the account. Those are the actual things that can go wrong. The connection is not failing because HubSpot is unsupported; it is failing because the token, portal, or app permissions do not match the company’s setup.

Use HubSpot when the company needs CRM context inside LenGrowth and the team wants pipeline health to influence reporting and task prioritization. If the company does not use HubSpot, or if the portal is not the source of truth for the business, the integration will not be useful. The value is in matching the company workspace to the exact CRM portal that reflects the business being worked on.

The page also keeps the private-app workflow visible in one place, which helps the user confirm the token belongs to the correct portal before leaving the modal. That is a useful guardrail when a team has multiple HubSpot portals or when an agency manages several clients and needs to keep them distinct.

The selected source label is also useful later when the company returns to the integrations page. It helps the team see whether LenGrowth is still reading the intended portal or whether the private app token should be rotated and reconnected.

That makes the source easy to audit without reopening HubSpot itself.

It is the quickest way to confirm the CRM link still matches the company.

Related pages: