Calling from Contact View triggers onDialNumber event in Calling Extensions SDK with unintended objectId

Develop, Build & Integrate APIs & Integrations
1

Summary

We are developing a calling application for call integration using the Calling Extensions SDK (GitHub - HubSpot/calling-extensions-sdk: A JavaScript SDK for integrating calling apps into HubSpot. · GitHub).

It appears that in the HubSpot CRM contact view (/contacts/:id/objects/0-1/views/all/list), the onDialNumber event is sometimes triggered with an unintended objectId when initiating a call by clicking a phone number for a specific contact record.

Issue Details

Steps to Reproduce

  1. Open the HubSpot CRM contact view (/contacts/:id/objects/0-1/views/all/list).

  2. Open the detail view for any contact record (Contact A) (/contacts/:id/record/0-1/:objectId) and initiate a call using the “Call” button → In this case, the onDialNumber event is triggered with the correct objectId set.

  3. Return to the HubSpot CRM contact view (/contacts/:id/objects/0-1/views/all/list) using the web browser’s back button.

  4. From the HubSpot CRM contact view (/contacts/:id/objects/0-1/views/all/list), click the phone number in the “Phone Number” column for any contact record (Contact B) to initiate a call → In this case, the onDialNumber event is triggered with the objectId for Contact A instead of Contact B.

Expected Behavior

In step 4 of the “Steps to Reproduce” above, the objectId for Contact B should be passed.

Impact

The calling application incorrectly assumes that a call was made to an unintended contact.

2

You should use read calleeInfo.calleeId