[FEATURE] HubSpot: Removing Support for Referencing Custom Object Types by Base Name

[vunguyenhung]

Is your feature request related to a problem? Please describe.
Quote from HubSpot email as below. Please check our HubSpot component code where we referencing Custom Object Types by Base Name, and update to use unique identifier instead. Please see the quote below for more details

Hi Pipedream,

On Tuesday, April 29, HubSpot removed the undocumented support for requesting custom object types by their base name in HubSpot public APIs.

May 2025 update: Although we have been communicating this change since October 2024, the message did not reach all impacted customers and non-partner developers as intended. Therefore, we'll be extending the time to adopt the new request format to June 4, 2025. At that point, HubSpot will once again stop support for using the base name format in API calls for custom objects. There will not be any further extensions, so we recommend that all developers follow the guidance here as soon as possible.

Your app (App ID: 208642) was identified as recently using undocumented functionality for referencing custom object types by their base name.

As a primary contact for your business, you may be the only one who received this message. Please read below and forward along as needed.

What's happening?

On June 4, 2025, HubSpot will be removing the undocumented support for requesting custom object types by their base name in HubSpot public APIs.

All custom object types must be referenced by their unique identifier (object type ID, fully qualified name, or short-hand custom object type name) to ensure clarity and consistency in API interactions.

Please review this changelog post for more technical details.

Why is HubSpot making this change?

HubSpot is actively developing and releasing new HubSpot-defined object types for customers’ commonly requested use cases.

Removing this undocumented support in our public APIs will help prevent conflicts when HubSpot-defined object types are released in portals where a custom object has the same name.

Next steps:

• Update your app to ensure that all API requests to custom object types comply with the documented requirements and no longer refer to a custom object type by its base name.
• Please refer to our API documentation for more information on retrieving custom object type data and understanding the available reference formats.
• Fill out this support form for help with any technical questions.

Failure to update your app before June 4 will result in unexpected errors or a failed request, creating a poor experience for customers.

We appreciate your compliance and understanding as we look to best serve our mutual customers. Thank you for being a valued app partner.

Best,

The HubSpot App Partner Team

Describe the solution you'd like
A clear and concise description of what you want to happen.

Do you have a workaround?
Are you able to tackle the problem with an existing workaround, or can you not move forward without this feature?

Comparable features in other tools?
Is this feature or one like it available in another platform? If so, we'd love to hear what you like about that implementation.

Additional context
Add any other context or screenshots about the feature request here.

[vunguyenhung]

Hi everyone, all test cases are passed! Ready for release!

Test report
https://vunguyenhung.notion.site/FEATURE-HubSpot-Removing-Support-for-Referencing-Custom-Object-Types-by-Base-Name-1eebf548bb5e8169a74fc2f65f683a2d