HubSpot for Dialpad Release Notes

Prev Next

Dialpad continuously improves its HubSpot integration, so you always have access to the latest features and fixes. This article covers upcoming changes to the HubSpot for Dialpad integration specifically — for broader platform updates, visit the Dialpad Release Notes.

Note

Dialpad is committed to providing you with the best possible product. Our features undergo rigorous quality assurance (QA) testing, and we are picky! While we do our best to release the features on the dates listed in this article, if our QA team finds something that's not working exactly as we want, we will delay the feature and push it to the following release.

April 16, 2026

Improvement

‘Times Dialed’ field now locks after the Power Dialer list is activated

A new "Contact Management" setting has been added to automatically create a HubSpot contact when no existing match is found, covering events such as answered and missed calls, voicemails, and inbound/outbound SMS. Contact creation uses reliable Dialpad-side data (phone number, name, email, company) and includes deduplication safeguards to prevent race conditions in contact center call flows. The setting is disabled by default.

Bug fixes

Unable to set up SMS workflow

Some users were unable to configure SMS workflows in HubSpot, encountering an error stating that the third-party app could not verify field values, and the sender field displayed no available options. This has been fixed.

HubSpot contact sync failures due to phone number format and timeout errors

A few users reported that their contacts configured to sync from HubSpot to Dialpad were not appearing as expected, with BQ logs showing recurring "Office reference failed" errors and timeouts on the entegreeder endpoint. We’ve fixed this.

Duplicate call records created in HubSpot for DTMF-transferred calls from mainline

Sometimes, when an inbound call to a mainline number was routed via DTMF transfer to a Contact Center queue, HubSpot logged both a missed call record and an answered call record for the same call session. This has been fixed.

Dialpad AI data not logging to HubSpot call activities

Dialpad AI-generated data, including AI Recap and transcription, was not being included in the corresponding HubSpot call logs even when AI was enabled at the office level and the "Add AI-generated data" setting was turned on. We’ve fixed this.

April 2, 2026

New

Route HubSpot tickets by pipeline

Direct automatically created tickets to the right team by selecting specific HubSpot pipelines for missed calls, voicemails, or SMS.
Learn more.

March 2, 2026

This release includes updates to Dialpad for Salesforce and does not require a package update — just open the Dialpad app to see the new features and functionality.

Improvement

Call title not saving on first call log

A few users noticed that the call title was not saved correctly d

Improvement

Add setting to disable call logging when no contact match is found (DP-170715): A new boolean setting, "Log calls when a match is found," has been added to the HubSpot integration, allowing users to restrict call logging to only those calls where a Dialpad contact is successfully matched to a HubSpot record. This setting is placed within the "Log calls as activities" section and defaults to false to preserve existing behavior. No feature flags are involved.

Prevent duplicate SMS messages from HubSpot Workflows (DP-143147): HubSpot Workflow triggers could cause the same SMS message to be sent multiple times to a recipient, particularly when multiple tickets with identical content were processed simultaneously. A deduplication mechanism has been implemented to suppress outbound messages that share the exact same body sent to the same recipient within the same hour. This ensures recipients receive each intended message only once.

Reduce workflow SMS error log noise and add descriptive logs (DP-173592): False error entries were being generated in the HubSpot workflow SMS pipeline, creating unnecessary log noise that obscured genuine issues. Additional logging was introduced to capture the sender and recipient phone numbers involved in SMS workflow actions. These changes improve observability and make it easier to diagnose real failures.

Bug fixes

Contact properties 'Last inbound message' and 'Last inbound message timestamp' update bug

The Dialpad integration properties for tracking inbound SMS — Last inbound message and Last inbound message timestamp — were not updating on HubSpot contact records when an inbound SMS was received. This prevented customers from setting up workflows to automatically notify contact owners on inbound messages. The issue was resolved.

March 26, 2026

This release includes updates to Dialpad for Salesforce and does not require a package update — just open the Dialpad app to see the new features and functionality.

Bug fixes

Intermittent Call Activity logging

Some users reported that, on every second call, the Salesforce CTI failed to load the wrap-up screen at call hang-up, resulting in call activity for matched contacts not being logged in Salesforce.

Field mapping label not displaying correctly for custom object