Skip to content

Commit e9ed21e

Browse files
author
Gaurav Kochar
committed
Moved this banner to top
1 parent c371fd2 commit e9ed21e

File tree

1 file changed

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

1 file changed

+9
-8
lines changed

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

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,15 @@ HubSpot is an all-in-one marketing tool that helps attract new leads and convert
1616

1717
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"}.
1818

19+
> warning ""
20+
> As of April 29, 2025, HubSpot will no longer support referencing custom object types by their base names. HubSpot mandates that custom objects should be referenced by short-hand custom object type name, fullyQualifiedName, or objectTypeId. To avoid issues, ensure the following fields are updated accordingly:
21+
>
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
25+
>
26+
> For further details, please refer to the official HubSpot documentation [here](https://developers.hubspot.com/changelog/breaking-change-removed-support-for-referencing-custom-object-types-by-base-name).
27+
1928
> warning ""
2029
> 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.
2130
>
@@ -24,14 +33,6 @@ When you use the HubSpot Cloud Mode (Actions) destination, Segment sends your da
2433
> warning ""
2534
> **Behavioral Events (Legacy)** are only supported with [Hubspot Classic Destination](/docs/connections/destinations/catalog/hubspot/).
2635
27-
> As of April 29, 2025, HubSpot will no longer support referencing custom object types by their > base names. HubSpot mandates that custom objects should be referenced by shorthand name, fully > qualified name, or object type ID. To avoid issues, ensure the following fields are updated
28-
> accordingly:
29-
>
30-
>- **Object Type** and **ObjectType to associate** in **Upsert Custom Object Record** action
31-
>- **Object Type** field in **Custom Event V2** action
32-
>- **Object Type** and **To Object Type** fields in **Custom Object V2** action
33-
>
34-
> For further details, please refer to the official HubSpot documentation [here](https://developers.hubspot.com/changelog/breaking-change-removed-support-for-referencing-custom-object-types-by-base-name).
3536

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

0 commit comments

Comments
 (0)