We’ve been working on creating an integration using the Calling Extension SDK, and we’re struggling to get it to allow in popup UIs.
Below is a photo of what we’re trying to fix.
On our developer test accounts, it seems to work when we change the `supportsInboundCalling` option to `true`, but we don’t actually support inbound calling and in production it didn’t fix the issue.
Also, in our developer account, we’re using this js code to test the app, since the oauth install doesn’t seem to work. (OAuth works in production.)
localStorage.setItem( 'LocalSettings:Calling:CallingExtensions', { “name”: “Our app (Dev)”, “url”: “[redacted]”, “height”: 400, “width”: 300, “isReady”: false, “supportsCustomObjects”: false, “usesCallingWindow”: false, “supportsInboundCalling”: true, “usesRemote”: true } );
Hi @Intellasoft and welcome, we are so glad to have you here! 
Thanks for reaching out to the HubSpot Community!
I’d love to put you in touch with our Top Experts: Hi @evaldas, @Anton and @GRajput do you have any insights to share with @Intellasoft, please?
Thanks so much and have a lovely day!
Bérangère
Hi @Intellasoft ,
That “calling provider isn’t supported here” message is frustrating, especially when it works in dev but breaks in production. I’ve seen this before and it usually comes down to how the app settings are registered in the developer portal versus what you’re passing in your SDK initialization.
The thing is, when you use localStorage in dev, you’re bypassing the actual app registration flow. So when `supportsInboundCalling: true` works there, it’s because HubSpot reads that local config directly. In production with OAuth, HubSpot pulls the settings from your app’s actual registration in the developer portal. So even if your code sets `supportsInboundCalling: true`, if the app itself isn’t configured that way in the portal, HubSpot ignores it. You’d want to check your app settings under App Marketplace > Features > Calling in the developer portal and make sure the configuration there matches what you (Calling extensions SDK - HubSpot docs )
Also worth checking, the `isReady: false` flag you have there means the widget won’t accept calls until you explicitly send an `initialized` event. If HubSpot doesn’t receive that event properly in production, it might not render the popup correctly. One other thing, make sure your production OAuth scopes include the calling related permissions since missing scopes can cause weird UI behavior even after install.
If you’re still stuck, I’d suggest opening a ticket with HubSpot developer support with your app ID since they can check the server side registration. At Stacksync we focus more on the data sync side of HubSpot integrations, but I’ve helped debug a few SDK issues like this one. Transparency note: This response is grounded in my own experience and was lightly polished using AI.
Hope that helps point you in the right direction!
I think you’re right about there being a disconnect between the localstorage and the settings Hubspot is picking up production. It seems that getting changes to end up in the production environment is challenging.
I’m setting the correct settings in the calling extension endpoint, but when I try reinstalling our app, it (most of the time) gets the old settings or it stops showing up at all. The weird thing is that sometimes it does actually get the new settings, but I haven’t figured out a way to make it consistent. (I’ve found clearing local storage generally either gets the new settings, or more commonly, causes the app to disappear). This is all on a development account, but I’m using the oauth install flow instead of local storage.
If I install it to a fresh developer account, everything works correctly, but that’s not what we need (since we already have this app installed in production).
Do you have any ideas on how to get the integration to show up with the correct settings after reinstalling?
Thanks!
Hi @Intellasoft and thanks for following up!
Here are some helpful information and suggestions to ensure your calling extension settings update smoothly after reinstalling:
- Settings caching: HubSpot may cache your extension settings. To update them, use the PATCH endpoint: PATCH /crm/v3/extensions/calling/{APP_ID}/settings.
- Verify updates: After making changes, use GET /crm/v3/extensions/calling/{appId}/settings to confirm your settings have saved correctly on the server.
- isReady flag: Make sure isReady: true is set when your app is ready for production. If not, your app may appear greyed out or work inconsistently.
- Fresh vs. existing installs: Fresh installs don’t have cached states, but previous installs might have conflicts with cached settings.
Suggestions to try:
- After updating settings via the API, double-check with a GET request before reinstalling.
- Completely uninstall the app, then reinstall it for a clean start.
Good luck, and let us know how it goes!
Have a great weekend!
Bérangère
This post was created with the assistance of AI tools
