HubSpot Calling Extensions: Setup, Scopes, and Avoiding Gotchas

Diving into HubSpot's Calling Extension SDK can unlock powerful integrations for your CRM, connecting your communication tools directly into your HubSpot workflow. A recent HubSpot Community thread highlighted some key questions around setting up and configuring these extensions, offering valuable insights for developers and RevOps teams alike.

Understanding the Calling Extension Setup

The original poster in the community sought clarity on the proper method for enabling the Calling SDK for their custom CTI connector, inquiring whether the PATCH endpoint (/crm/v3/extensions/calling/{app_id}/settings) was the standard approach. They also asked for confirmation on the necessary scopes for their developer account.

One respondent clarified that there isn't a separate "activation" step for Calling Extensions. Instead, HubSpot recognizes your calling provider as available once you've configured the calling settings for your app. Setting isReady to true signals that your app is ready for users to select within HubSpot.

Another community member provided links to helpful resources, including the HubSpot developer documentation and a related community thread, expanding the context.

Essential Scopes for Calling Extensions

The discussion also addressed the critical aspect of required scopes. According to one of the replies, the minimum scopes needed for a Calling Extension are:

• contacts
• timeline

These scopes grant access to contacts and enable HubSpot to create and update call engagements on the CRM timeline. However, another experienced community member wisely suggested considering future needs. If your connector requires accessing associated companies or deals during a call (for features like screen pops), it's best to request those additional scopes upfront to avoid re-authorization hassles later.

Key Takeaways and Avoiding Common Pitfalls

Here's a summary of the essential points from the HubSpot Community discussion:

1. No Separate Activation: Calling Extensions are enabled by configuring settings and setting isReady to true.
2. Essential Scopes: contacts and timeline are the minimum required scopes.
3. Plan Ahead: Anticipate future data access needs (companies, deals, etc.) and request those scopes early.
4. Test Thoroughly: The development portal and live environment can behave differently. Always test the full flow in a developer test account before deploying to production.

ESHOPMAN Team Comment

This thread highlights the importance of careful planning when integrating with HubSpot's APIs. We at ESHOPMAN appreciate the practical advice about testing in a development environment and anticipating future scope requirements. These are crucial steps to ensure a smooth and scalable integration, especially when building a store builder or other complex application on top of HubSpot.

By carefully considering these points, you can streamline your Calling Extension development and create a more robust and valuable integration for your HubSpot users. Remember to leverage the HubSpot Community for ongoing support and best practices as you build!