Skip to content

Commit fdddab0

Browse files
author
Gaurav Kochar
committed
Added Warning for breaking changes in hubspot for refering custom objectTypes by base names
1 parent 6ce4b1b commit fdddab0

File tree

1 file changed

+7
-0
lines changed
  • src/connections/destinations/catalog/actions-hubspot-cloud

1 file changed

+7
-0
lines changed

src/connections/destinations/catalog/actions-hubspot-cloud/index.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,6 +24,13 @@ When you use the HubSpot Cloud Mode (Actions) destination, Segment sends your da
2424
> warning ""
2525
> **Behavioral Events (Legacy)** are only supported with [Hubspot Classic Destination](/docs/connections/destinations/catalog/hubspot/).
2626
27+
> warning ""
28+
> After April 29, 2025, HubSpot will no longer support referrals to custom object types by their base name.
29+
> If you use **Upsert Custom Object Record** ensure you have selected **Object Type** and **ObjectType to associate** field from dropdown.
30+
> If you use **Custom Event V2** , ensure you have selected **Object Type** field from dropdown.
31+
> If you use **Custom Object V2** , ensure you have selected **Object Type** and **To Object Type** field from dropdown.
32+
> 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)
33+
2734

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

0 commit comments

Comments
 (0)