Skip to content

Commit b97515c

Browse files
Update src/connections/destinations/catalog/actions-hubspot-cloud/index.md
Co-authored-by: stayseesong <[email protected]>
1 parent c132454 commit b97515c

File tree

1 file changed

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

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -19,9 +19,9 @@ When you use the HubSpot Cloud Mode (Actions) destination, Segment sends your da
1919
> warning ""
2020
> As of April 29, 2025, HubSpot no longer supports referencing custom object types by their base names. Instead, you must reference all custom objects by using their short-hand custom object type name, `fullyQualifiedName`, or `objectTypeId`. To avoid issues, update the following fields:
2121
>
22-
>- **Object Type** and **ObjectType to associate** in **Upsert Custom Object Record** action
23-
>- **Object Type** field in **Custom Event V2** action
24-
>- **Object Type** and **To Object Type** fields in **Custom Object V2** action
22+
>- **Object Type** and **ObjectType to associate** in the **Upsert Custom Object Record** action
23+
>- **Object Type** field in the **Custom Event V2** action
24+
>- **Object Type** and **To Object Type** fields in the **Custom Object V2** action
2525
>
2626
> 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"}.
2727

0 commit comments

Comments
 (0)