Skip to main content
The First Step
October 9, 2026
Question

Can a custom HubSpot connector use App Connect’s voicemail-drop feature?

  • October 9, 2026
  • 2 replies
  • 11 views

I saw the related HubSpot discussion stating that RingEX does not support voicemail drop natively. My question is specifically about the voicemail-drop feature documented for App Connect:

https://appconnect.labs.ringcentral.com/users/voicemail-drop/

I would like to develop a custom HubSpot connector for App Connect using RingCentral RingEX, with HubSpot contact lookup and call activity logging.

Can a custom CRM connector reuse App Connect’s existing voicemail-drop feature, including its AI transfer, beep detection, and recording playback service? Are there any licensing, provisioning, or connector requirements?

Also, which current developer documentation and starter project should I use?

I have posted the fuller technical questions on GitHub:

 ringcentral/rc-unified-crm-extension#253

 

 

2 replies

ByrneReese
Community Manager
Product Manager
October 9, 2026

You are welcome to create a Hubspot connector on App Connect - and I hope you might even consider making it available for others to use (but that is another post!). 

To create a connector, it is quite easy (or I would like to think so) - get started here: https://appconnect.labs.ringcentral.com/developers/getting-started/

And yes - any connector can utilize App Connect’s voicemail drop feature. There is no additional charge or license required at this time. 

morganclThe First StepAuthor
The First Step
October 9, 2026

Hi Byrne—thanks again for confirming that custom connectors can use voicemail drop.

I followed the Developer Console’s Quick Setup: 

npx @app-connect/cli init morgan_clark.sample_connector

The CLI (@app-connect/cli@0.1.5) created the project from the GitHub main-branch template, but dependency installation failed:

npm error notarget No matching version found for @app-connect/core@^2.0.0

The generated package.json specifies "@app-connect/core": "^2.0.0". Checking the public npm registry shows:

latest: 1.7.44

beta: 1.7.0-beta.6

No published 2.0 version in the returned version list.

Should we use a different template branch or package version, or is the 2.0 core package still awaiting publication?

We’re testing with the App Connect Release Candidate extension, version 2.1.0.