Skip to content

[STRAT-5744]| Added Warning for breaking changes in Hubspot for referring custom object Types by base names. #7578

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 9 commits into from
Apr 24, 2025
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,13 @@ When you use the HubSpot Cloud Mode (Actions) destination, Segment sends your da
> warning ""
> **Behavioral Events (Legacy)** are only supported with [Hubspot Classic Destination](/docs/connections/destinations/catalog/hubspot/).

> warning ""
> After April 29, 2025, HubSpot will no longer support referrals to custom object types by their base name.
> If you use **Upsert Custom Object Record** ensure you have selected **Object Type** and **ObjectType to associate** field from dropdown.
> If you use **Custom Event V2** , ensure you have selected **Object Type** field from dropdown.
> If you use **Custom Object V2** , ensure you have selected **Object Type** and **To Object Type** field from dropdown.
> For More information, refer to hubspot documentation [here](https://developers.hubspot.com/changelog/breaking-change-removed-support-for-referencing-custom-object-types-by-base-name)


## Benefits of HubSpot Cloud Mode (Actions) vs HubSpot Classic
HubSpot Cloud Mode (Actions) provides the following benefits over the classic HubSpot destination:
Expand Down