HubSpot Release Notes

Release notes are displayed in descending order from the most recent release to the oldest. Known Issues are listed with the most recent release.

See TIBCO Scribe® Online Connector For HubSpot for more information.

Note: To access any changes to metadata support, such as new operations, entities, or fields, reset metadata for the Connection. See Resetting Metadata.

Version 4.11.0 Release

Released March 16, 2023.

New And Noteworthy

A new field, titled Additional Scopes, has been added to the Connection dialog to enable the use of scopes when making HTTP calls to the HubSpot API using the Send block. (SCHUB-232) (Case # 02064649)

The operations associated with the Engagement entity have been updated to use new HubSpot APIs to return engagements by ID. Previously they were returned by the engagement's association with another entity, such as Contacts. [SCHUB-2]

Changes In Functionality

The operations associated with the Engagement entity have been updated. They now use new HubSpot APIs to return engagements by ID. Previously they were returned by the engagement's association with another entity, such as Contacts. (SCHUB-2)

Closed Issues

SCHUB-557

Querying the Engagement entity with a filter on the LastUpdated datetime field failed with an error similar to the following: (Case # 02172194, 02173793)

Error reading string. Unexpected token

SCHUB-550

Configuring a new HubSpot connection failed with the following error: (Case # 02170066)

The redirect_uri doesn't match the client registered redirect_uri. Please contact the app developer.

SCHUB-453

Connecting to a new HubSpot account generated errors similar to the following:

Error Details - Couldn't complete the connection Insufficient scopes were provided. Please contact the app developer.

This issue was addressed by allowing users to configure Scopes on the Connection dialog. (Case ID: 02089703)

Known Issues

SCHUB-11

Summary: When Querying the Deal entity, the CompanyId value is returned as NULL. (Case # 01755284)

Workaround: If you need to include the CompanyId, use a Lookup Block to retrieve it before writing the Deal record to a target datastore.

14358

Summary: Query and Update operations are unsuccessful when filtering by an email address that contains special characters, such as ?. Period, underscore, greater than (>), and less than (<) are supported.

Workaround: None.

64265 / 66610

Summary: When configuring Match Criteria for an Update, putting a list array field in a TODOUBLE function, generates errors and the update fails. (Case # 64744)

Workaround: None.

66609

Summary: Custom field data does not display in the Query Preview tab when filtering Contacts by ContactListID. Note that the data does not display but is included in the record and is part of the integration. (Case # 65876, 66132)

Workaround: If possible, use a different filter.

Version 4.10.0 Release

Released February 25, 2022.

New And Noteworthy

There are no new features in this release.

Changes In Functionality

The connector now supports the HubSpot API change of splitting the contacts scope into more granular CRM scopes. A scope provides access to a specific set of HubSpot API endpoints. Making the scopes more granular improves security by only providing access to a limited number of API endpoints. Supported scopes include:

Note: For existing connections, users might get authentication errors due to the HubSpot API change. To resolve this, open the existing connection, re-authenticate by clicking the Authenticate button, and select OK to save the connection.

Closed Issues

There are no closed issues in this release.

Known Issues

SCHUB-11

Summary: When Querying the Deal entity, the CompanyId value is returned as NULL. (Case # 01755284)

Workaround: If you need to include the CompanyId, use a Lookup Block to retrieve it before writing the Deal record to a target datastore.

14358

Summary: Query and Update operations are unsuccessful when filtering by an email address that contains special characters, such as ?. Period, underscore, greater than (>), and less than (<) are supported.

Workaround: None.

64265 / 66610

Summary: When configuring Match Criteria for an Update, putting a list array field in a TODOUBLE function, generates errors and the update fails. (Case # 64744)

Workaround: None.

66609

Summary: Custom field data does not display in the Query Preview tab when filtering Contacts by ContactListID. Note that the data does not display but is included in the record and is part of the integration. (Case # 65876, 66132)

Workaround: If possible, use a different filter.

Version 4.9.0 Release

Released November 2, 2021.

New And Noteworthy

Added Send operation functionality which is used to make API calls to the HubSpot API. The Send operation supports the Request entity used to build the HTTP call to the API.

Changes In Functionality

The expiration period for OAuth access tokens is reduced to 30 minutes from 6 hours.

The connector supports two Add blocks that are used in different circumstances.

Closed Issues

SCHUB-40

When creating or updating a record in HubSpot where one of the fields has a float input value of '0', that value is converted to NULL. (Case # 01886258)

SCHUB-34

Querying engagements that are type Email, IncomingEmail, or ForwardedEmail does not support returning the contents of those emails. (Case # 01861067 01873721)

SCHUB-28

Querying the Deal entity with the Net Change filter enabled causes long delays returning the selected records. (Case # 01817666)

 

Version 4.8.1 Release

Released June 26, 2019.

New And Noteworthy

There are no new features in this release.

Changes In Functionality

As of June 28, 2019 HubSpot will no longer support the Print and Forward email event types. In TIBCO Cloud™ Integration - Connect on the Block Properties Fields Tab you can see a list event types in the description for the type field on the EmailEvent entity. That list has been updated and no longer includes the Print and Forward email event types. In addition, these types can no longer be used as filters. (75938)

Note: This change requires that you reset metadata for your HubSpot Connection on or after June 28, 2019.

The EmailEvent entity is only available for Query, Lookup, and Fetch operations. If you have used either the Print or the Forward event type as a filter for any of these operations, you must update your flows to remove those filters. If a flow executes using Print or Forward as a filter, an error similar to the following is generated:

ERROR: Exception Type : InvalidExecuteQueryException
Message : The following error has occurred in the HubSpot Connector: NOTE: As of June 28, 2019, the values PRINT and FORWARD are no longer valid.
Cannot convert filter value to EmailEventType, valid values are: SENT, DROPPED, PROCESSED, DELIVERED, DEFERRED, BOUNCE, OPEN, CLICK, STATUSCHANGE, SPAMREPORT

Closed Issues

77268 / SCHUB-6 / SCHUB-17

When a NULL value was mapped to the companyId field for a Deal, errors similar to the following were generated: (Case # 01753994)

"Operation failed. Label: Update/Insert Deal, Name: DealUpdateInsert, Message: An unexpected error occurred.: Error in calling Operation DealUpdateInsert Create successful for deal but unable to associate company with id: 0 to deal with id: 727620758. Hubspot error message: Invalid input JSON on line 6, column 1: toObjectId must be > 0.

76722 / SCHUB-3

HubSpot number data types were being converted to Int32 instead of BigInt. This caused errors when working with ID numbers that exceeded the size of the Int32 data type. (Case # 01746092, 01746815)

Note: For this change to take effect you need to reset metadata for your HubSpot Connection.

Version 4.7.1 Release

Released April 24, 2019.

New And Noteworthy

Updated the operations associated with the Contact entity to use new HubSpot APIs to associate a Contact with another HubSpot object or remove that association. (75679)

Updated the operations associated with the Deal entity to use new HubSpot APIs to associate a Deal with another HubSpot object or remove that association. (75783)

Added a new CRMAssociations entity used to Query, Create, or Delete associations between objects in HubSpot, such as the association between a deal and a company. (75699)

Changes In Functionality

On April 26, 2019 HubSpot will make the associatedcompanyid field on the Contact entity read-only and will launch a new CRM Associations API to manage associations for many HubSpot objects. TIBCO Scribe® has modified the HubSpot Connector to accommodate these changes and allow your existing flows to execute without any changes on your part. However, due to the changes to the HubSpot API, you may experience some degradation in performance and increased API calls when a flow contains the following:

If you experience a degradation in performance or exceed your API limits, try dividing the process into separate apps that execute on different days. For example, Create your Contacts on Day 1 and Update those Contacts with an associatedcompanyId on Day 2 using the new CRMAssociations entity.

Closed Issues

74860 / 74930

In the Contact entity metadata, when a custom field had the same name as the reserved field portalId, the HubSpot Connector generated errors similar to the following: (Case # 69633)

An item with the same key has already been added.

 

Version 4.6.1 Release

Released January 18, 2019.

New And Noteworthy

Included portalId field on the Contact entity. This field could be used if you chose to construct your own Contact URL. (73339)

Changes In Functionality

Contact Entity

HubSpot is deprecating access to its Public Contact record on January 23, 2019. In prior versions of the Connector for HubSpot the profileurl virtual field on the Contact entity contained the URL for the Public Contact record. In this release, the following updates have been made in response to these HubSpot changes:

  1. If you are not using the profileurl field, you do not need to do anything.
  2. If you are using the profileurl field to generate the Contact Timeline URL and you want to continue using it, leave your flows as they are, but note that the results will change on January 23, 2019.
  3. If you are using the profileurl to retrieve the Contact URL, it is recommended that you switch to the supported Contact URLs by modifying your flows to use the two new virtual fields. After the January 18, 2019 Connector for HubSpot update is released, reset metadata for your HubSpot Connections. Once metadata is reset, modify your flows with the new Contact HubspotContactUrl and/or Contact HubspotContactTimelineUrl virtual fields.

Query EmailEvent

The Query operation for the EmailEvent entity has been enhanced and may include more records than it did in prior Connector versions. (66163, 73477)

When Querying the EmailEvent entity:

Closed Issues

66472 / 66163

Querying the EmailEvent entity and using Net Change to filter for new and updated records, returned only a subset of EmailEvent records that were greater than the Most Recent Record Processed date. (Case # 65747)

66187 / 66263

If new fields were added to the ContactList entity, but did not exist in the metadata cached by the Connector, using the Lookup Block to query ContactList generated errors and did not process the record. After this update to the Connector, the unknown field is ignored and the records are processed. (Case # 64474)

 

Version 4.5.1 Release

Released April 30, 2018.

New And Noteworthy

There are no new features in this release.

Closed Issues

63783

Extended the timeout value from 100 seconds to five minutes to address the following error: (Case # 64289)

A task was canceled.

 

Version 4.5 Release

Released April 12, 2018.

New And Noteworthy

Closed Issues

58401

Added Query support for the DealPipeline entity. (Case # 63032)

57992

When querying the Contact entity, the createdate field can be used either on the Net Change tab or on the Filter tab with the greater than or greater than or equal to operators to return only new Contact records. (Case # 63076)

59100

Existing HubSpot Connections were not automatically updated to use OAuth 2.0. Users had to delete and recreate their Connections to generate and save the new OAuth 2.0 authentication token. (Case # 64009)

61224

Invalid email addresses found when querying HubSpot engagement records caused the following error: (Case # 63736)

Object reference not set to an instance of an object.

 

Version 4.4.1 Release

Released January 30, 2018.

New And Noteworthy

Updated the API endpoint used for the Form entity to a HubSpot V2 API Endpoint. (55070)

Note: Forms created in the HubSpot UI can contain rich text fields used to display descriptions or notes about the Form. The information contained in those fields is not actual Form data, but part of the Form itself.

The contents of these fields were returned in the metadata for the Form entity from the HubSpot V1 API endpoint and could be mapped. Now that the Connector uses the HubSpot V2 API endpoint, the rich text fields are no longer provided in the metadata as fields, but as a property that cannot be modified and cannot be mapped.

If you have any of these rich text fields mapped in the Submit operation of a flow, the Connector will ignore them when comparing them to the metadata and will pass them through to HubSpot in the Submit target operation. However, best practice would be to reset metadata and remove them from your flows. Field names displayed for the rich text fields in the TIBCO Cloud™ Integration - Connect field mapper are similar to the following:

hs_rich_text_213709b622c40374cc821a587b522637b3d36358

Closed Issues

57601 / 58230

Querying the Engagement entity for a small number of records sometimes generated the following error: (Case # 62649)

Error converting value {null} to type 'System.Int32'. Path 'offset', line 1, position 1251. Null object cannot be converted to a value type. "

Version 4.4 Release

Released November 10, 2017.

New And Noteworthy

Closed Issues

31084

Improved error handling to provide more detailed information around the cause of the error. For example, in cases where a custom field has the same name as a standard field, the name of the field generating the error is provided in the error message. (Case # 87607, 58555)

50633 / 51841 / 52049

Updated the HubSpot Connector to treat page-id field values as strings instead of numeric data types to return records with non-numeric values in those fields correctly. (Case # 61037)

52320 / 52332

When querying the Deals entity, the includeAssociations parameter was included twice in the request generating the following error: (Case # 61156)

HttpStatus: BadRequest. Message: Error binding request parameters

 

Version 4.3 Release

Released September 11, 2017.

New And Noteworthy

Closed Issues

49235

The Connector now throttles API calls and increases the number of retries when using HubSpot to avoid exceeding API limits which generated errors similar to the following: (Case # 59206, 60266)

Error in calling Operation Update: Operation failed. Label: Update Company, Name: CompanyUpdate, Message: You have reached your secondly limit. System.Exception: You have reached your secondly limit.

 

July 24, 2017 Release

New And Noteworthy

Support for OAuth 2.0 authentication. (44960)

Note: HubSpot has announced that it is ending support for OAuth 1 as of August 11, 2017. Existing Connections that use OAuth1 should continue to work until December 31, 2017. This change to the HubSpot API requires that you reauthenticate your HubSpot Connections.

Closed Issues

There are no closed issues in this release.

 

June 29, 2017 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

46660

Enhanced Connector to use the appropriate parsing function when it encountered HTML data in a response from the application. (Case # 58251)

June 7, 2017 Release

New And Noteworthy

Enhanced calls to the HubSpot API to ensure that API rate limits are not exceeded. (44396)

Closed Issues

37559

Querying Deals with relationships sometimes generated the following error when running a app even though running individual flows did not: The given key was not present in the dictionary. (Case # 56032)

44897

Updating ContactLists sometimes generated the following error: The given key was not present in the dictionary. (Case # 59057)

43319

Metadata retrieval failed if form data was not returned successfully from the HubSpot API. (Case # 58262)

38374

Query Preview failed when the entity being queried had a large number of custom fields. (Case # 55583)

37648

Metadata failed to load when a Vertical Tab was included as a picklist value. (Case # 55995)

36597

Querying Contacts and including the related child FormsSubmissionInfo entity, generated the following error in some HubSpot environments: Unable to find the field canonical-url for the entity FormsSubmissionInfo in the metadata cache. Parameter name: canonical-url (Case # 51232)

 

March 2016 Release

New And Noteworthy

Closed Issues

11621

HubSpot connection OAuth authentication sometimes failed with a 401 (Unauthorized) Http request error. This prevented the Connector from reconnecting later unless the user edited the connection and saved, causing the Connector to acquire a new access token. (Case # 78109 72791 )

12650

Improved error handling to reveal more detailed error messages received from HubSpot, rather than display Object Reference errors. (Case # 79838 )

12855

Added more retry logic when app jobs fail with 500 Internal errors or 504 Gateway Timeouts. (Case # 79838 )

12856

Querying Companies and related Contacts when there were or more 100 Contacts caused a timeout that sometimes generated an Object Reference error. (Case # 80016 )

12858

The HubSpot Connector was querying the Company/Contact relationship when it was not enabled. (Case # 80016)

 

September 2015 Release

New And Noteworthy

Added support for the following entities:

Closed Issues

There are no Closed Issues in this release.

 

July 2015 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

9993

Enhanced support for Source custom fields set to data type Date Picker. (Case # 72542 )

 

May 2015 Release

New And Noteworthy

Added date time support for Source custom fields set to data type Date Picker. (9831)

Closed Issues

9813

Enhanced error reporting to provide more detail when updating Contacts in HubSpot. (Case # 70908)

9864

Added correct date time support for target operations on custom fields set to data type Date Picker.

 

December 2014 Release

New And Noteworthy

There are no new features in this release.

Closed Issues

9056

Failure to update leads when matching against the contact email address field. (Case# 63315)

9140

When running multiple maps with HubSpot connections, the TIBCO Cloud™ Integration - Connect agent was updating connection parameters unnecessarily on every connect call.

 

June 2014 Release

New And Noteworthy

Closed Issues

8834

Parsing datetime fields for databases accessed by users that were not in a US locale caused a 401 error to be displayed. (Case # 59955)

Related Topics

Release Notes And Known Issues