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 @@ -16,6 +16,15 @@ HubSpot is an all-in-one marketing tool that helps attract new leads and convert

When you use the HubSpot Cloud Mode (Actions) destination, Segment sends your data to [HubSpot's REST API](https://developers.hubspot.com/docs/api/overview){:target="_blank"}.

> warning ""
> As of April 29, 2025, HubSpot will no longer support referencing custom object types by their base names. Instead, all custom objects must be referenced using their short-hand custom object type name, `fullyQualifiedName`, or `objectTypeId`. To avoid issues, update the following fields accordingly:
>
>- **Object Type** and **ObjectType to associate** in **Upsert Custom Object Record** action
>- **Object Type** field in **Custom Event V2** action
>- **Object Type** and **To Object Type** fields in **Custom Object V2** action
>
> For further details, refer to the [HubSpot documentation](https://developers.hubspot.com/changelog/breaking-change-removed-support-for-referencing-custom-object-types-by-base-name){:target="_blank"}.

> warning ""
> The **Upsert Company** action is not compatible with the Mapping Tester on the mappings page if Associate Contact is set to **Yes**. As a result, Segment recommends using the Event Tester or other tools to test and troubleshoot creating and updating companies in HubSpot.
>
Expand Down