From fdddab07a9d63b9135fc89b33beda4aa593d621c Mon Sep 17 00:00:00 2001 From: Gaurav Kochar Date: Mon, 21 Apr 2025 16:00:25 +0530 Subject: [PATCH 1/9] Added Warning for breaking changes in hubspot for refering custom objectTypes by base names --- .../destinations/catalog/actions-hubspot-cloud/index.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md index 4d8c70ccf8..c69de1c473 100644 --- a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md +++ b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md @@ -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: From c371fd2e4261a621dd1a431e59485058e8f51e5f Mon Sep 17 00:00:00 2001 From: Innovative-GauravKochar <117165746+Innovative-GauravKochar@users.noreply.github.com> Date: Tue, 22 Apr 2025 11:15:54 +0530 Subject: [PATCH 2/9] Update src/connections/destinations/catalog/actions-hubspot-cloud/index.md Co-authored-by: Varadarajan V <109586712+varadarajan-tw@users.noreply.github.com> --- .../catalog/actions-hubspot-cloud/index.md | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md index c69de1c473..93d624cefa 100644 --- a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md +++ b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md @@ -24,13 +24,14 @@ 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) - +> 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 +> 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, 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). ## Benefits of HubSpot Cloud Mode (Actions) vs HubSpot Classic HubSpot Cloud Mode (Actions) provides the following benefits over the classic HubSpot destination: From e9ed21ec60aee3c5a413ca80ce6fdf76999bb806 Mon Sep 17 00:00:00 2001 From: Gaurav Kochar Date: Tue, 22 Apr 2025 11:53:24 +0530 Subject: [PATCH 3/9] Moved this banner to top --- .../catalog/actions-hubspot-cloud/index.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md index 93d624cefa..13cfacab0b 100644 --- a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md +++ b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md @@ -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. 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: +> +>- **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, 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). + > 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. > @@ -24,14 +33,6 @@ 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/). -> 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 -> 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, 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). ## Benefits of HubSpot Cloud Mode (Actions) vs HubSpot Classic HubSpot Cloud Mode (Actions) provides the following benefits over the classic HubSpot destination: From 72ec99b99c419ae2446faea224b799840d7be98c Mon Sep 17 00:00:00 2001 From: Sharon Adewusi Date: Wed, 23 Apr 2025 13:29:52 +0100 Subject: [PATCH 4/9] wording and style changes --- .../destinations/catalog/actions-hubspot-cloud/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md index 13cfacab0b..16ccbe1090 100644 --- a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md +++ b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md @@ -17,7 +17,7 @@ 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. 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: +> 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 From bb6f73a3984b32b3dd710037a351d6e5074f22ac Mon Sep 17 00:00:00 2001 From: Sharon Adewusi Date: Wed, 23 Apr 2025 13:30:18 +0100 Subject: [PATCH 5/9] added target blank + wording change --- .../destinations/catalog/actions-hubspot-cloud/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md index 16ccbe1090..50c8dd2543 100644 --- a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md +++ b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md @@ -23,7 +23,7 @@ When you use the HubSpot Cloud Mode (Actions) destination, Segment sends your da >- **Object Type** field in **Custom Event V2** action >- **Object Type** and **To Object Type** fields in **Custom Object V2** action > -> 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). +> 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. From c1324545a8d8a7e652763ffc7fe8206c43b429cb Mon Sep 17 00:00:00 2001 From: Varadarajan V <109586712+varadarajan-tw@users.noreply.github.com> Date: Wed, 23 Apr 2025 23:04:33 +0530 Subject: [PATCH 6/9] Update src/connections/destinations/catalog/actions-hubspot-cloud/index.md Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> --- .../destinations/catalog/actions-hubspot-cloud/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md index 50c8dd2543..143fc1b71d 100644 --- a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md +++ b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md @@ -17,7 +17,7 @@ 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: +> 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: > >- **Object Type** and **ObjectType to associate** in **Upsert Custom Object Record** action >- **Object Type** field in **Custom Event V2** action From b97515c1d7bb66538871c8b4f028bb0cd0362dfc Mon Sep 17 00:00:00 2001 From: Varadarajan V <109586712+varadarajan-tw@users.noreply.github.com> Date: Wed, 23 Apr 2025 23:04:49 +0530 Subject: [PATCH 7/9] Update src/connections/destinations/catalog/actions-hubspot-cloud/index.md Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com> --- .../destinations/catalog/actions-hubspot-cloud/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md index 143fc1b71d..7a8b7c713b 100644 --- a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md +++ b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md @@ -19,9 +19,9 @@ When you use the HubSpot Cloud Mode (Actions) destination, Segment sends your da > warning "" > 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: > ->- **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 +>- **Object Type** and **ObjectType to associate** in the **Upsert Custom Object Record** action +>- **Object Type** field in the **Custom Event V2** action +>- **Object Type** and **To Object Type** fields in the **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"}. From b035aca351ff07fdb18de331a3b63d415b895736 Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Thu, 24 Apr 2025 09:53:06 -0700 Subject: [PATCH 8/9] Update src/connections/destinations/catalog/actions-hubspot-cloud/index.md --- .../destinations/catalog/actions-hubspot-cloud/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md index 7a8b7c713b..693fcf48c1 100644 --- a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md +++ b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md @@ -20,8 +20,8 @@ When you use the HubSpot Cloud Mode (Actions) destination, Segment sends your da > 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: > >- **Object Type** and **ObjectType to associate** in the **Upsert Custom Object Record** action ->- **Object Type** field in the **Custom Event V2** action ->- **Object Type** and **To Object Type** fields in the **Custom Object V2** action +>- **Object Type** in the **Custom Event V2** action +>- **Object Type** and **To Object Type** in the **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"}. From d6ef8c28c41761cdae7c80c0ca0f9c2f6ea271f1 Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Thu, 24 Apr 2025 10:09:02 -0700 Subject: [PATCH 9/9] changed format of other warning notes --- .../catalog/actions-hubspot-cloud/index.md | 12 ++++-------- 1 file changed, 4 insertions(+), 8 deletions(-) diff --git a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md index 693fcf48c1..8f1a219b6d 100644 --- a/src/connections/destinations/catalog/actions-hubspot-cloud/index.md +++ b/src/connections/destinations/catalog/actions-hubspot-cloud/index.md @@ -16,6 +16,10 @@ 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"}. +Keep in mind that: +* 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. For the company to contact association to work, you are required to trigger an Upsert Contact action before triggering an Upsert Company action. Contacts created with batch endpoint can not be associated to a Company from the Upsert Company Action. +* **Behavioral Events (Legacy)** are only supported with [Hubspot Classic Destination](/docs/connections/destinations/catalog/hubspot/). + > warning "" > 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: > @@ -25,14 +29,6 @@ When you use the HubSpot Cloud Mode (Actions) destination, Segment sends your da > > 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. -> -> Note that for the company to contact association to work, you are required to trigger an Upsert Contact action before triggering an Upsert Company action. Contacts created with batch endpoint can not be associated to a Company from the Upsert Company Action. - -> warning "" -> **Behavioral Events (Legacy)** are only supported with [Hubspot Classic Destination](/docs/connections/destinations/catalog/hubspot/). - ## Benefits of HubSpot Cloud Mode (Actions) vs HubSpot Classic HubSpot Cloud Mode (Actions) provides the following benefits over the classic HubSpot destination: