Connector for Zoom

This documentation references external sources. Nexthink does not have control over the accuracy of third-party documentation, nor any external updates or changes that might create inconsistencies with the information presented on this page. Please report any errors or inconsistencies to Nexthink Support.

The connector for Zoom allows you to measure and view call quality data and use the Nexthink web interface to investigate, troubleshoot and remediate Zoom call issues for well-informed decisions when optimizing the digital employee experience (DEX).


  • Users are part of Microsoft Azure Active Directory (Azure AD).

  • You have enabled the connector for Azure AD. Refer to the Connector for Microsoft Azure Active Directory documentation for more information.

  • User email addresses in Azure AD are the same as in the Zoom account.

  • Your Zoom account plan is Pro or Business+ (Business, Education, Enterprise & Partners).

Configuring the Zoom application

Configure the Zoom application from the Zoom App Marketplace page to retrieve call-quality data:

  1. Sign in using your Zoom credentials.

    • Ensure that you have permission to build applications. Typically, the system grants this action to account owners by default, however, you can manually grant permissions to appointed users.

  2. Navigate to the Develop option in the top-right corner of the Zoom App Marketplace page and select Build Server-to-Server app.

  3. Create and name the application.

  4. Copy and save the Account ID, Client ID and Client secret for future reference. That is, for the Nexthink connector configuration.

  5. Continue and complete the required fields under Basic Information and Developer Contact.

  6. Continue and copy the Secret Token to a safe location for future reference. That is, for the Nexthink connector configuration.

  7. Continue and click on Add Scopes to select the following permissions:

    1. Under the Meeting section: View all user meetings (meeting:read:meeting:admin, meeting:read:list_past_participants:admin)

    2. Under the Dashboard section: View all user's meetings information on dashboard (dashboard:read:meeting:admin, dashboard:read:meeting_participant_qos:admin, dashboard:read:list_meeting_participants_qos:admin, dashboard:read:list_meeting_participants:admin)

  8. Continue and Activate your app.

  9. Read the validation message to confirm your application activation.

Configuring the connector in the Nexthink web interface

From the Nexthink web interface:

  1. Select Administration > Inbound connectors from the main menu.

  2. Select Zoom from the list of inbound connectors.

  3. Enter the saved Account ID, Client ID, Client secret and Secret token as credentials for the Nexthink connector for Zoom. Refer to the Configuring the Zoom application section above.

  4. Save the Zoom inbound connector.

  5. Once saved, from the same Zoom inbound connector page, use the right-side panel to open the in-product documentation and copy the Event notification endpoint URL for future reference. That is, for the event subscription settings in Zoom.

Setting event subscriptions in Zoom

From the created and configured application in the Zoom App Marketplace:

  1. Go to the Feature section.

  2. Use the toggle to enable Event Subscriptions and select + Add Event Subscription.

  3. Enter the Subscription name.

  4. Paste the Event notification endpoint URL provided in the in-product documentation and Validate.

  5. Click + Add Events.

  6. From the Meeting section, select the End Meeting option and click on Done. This ensures Zoom sends out information when ending a meeting.

  7. Save the event subscription.

Known limitations

  • The system cannot retrieve call-quality data for macOS devices that are not on-premises AD joined.

  • Zoom limits the number of requests for call data to 30,000 per day for Pro accounts and 60,000 per day for Business+ accounts, respectively.

  • The system only retrieves data for the first 30,000 / 60,000 calls per day.


Do I need to change the settings if I previously configured the connector with the verification token.

The connector still relies on the verification token previously configured until it is deprecated. Please update the configuration with the new fields to ensure the connector works properly.

Do I always need to use the connector for Azure AD to obtain the call quality data?

Yes, the field used to identify between Nexthink users and users participating in a Zoom call is the email address.

The connector for Azure AD is required to enrich Nexthink users with the email address and create a match with the information provided by Zoom.

What happens if a user receives a call from a device that doesn’t have Collector installed?

Nexthink associates the call quality data information with the device as long as Collector runs on it. When the user logs in from a mobile phone, the Nexthink web interface provides information such as the mac_address and the type of connection but no device information.

Can I disable or remove the Zoom subscription?

The connector for Zoom does not allow you to disable or remove the subscription.

You can avoid processing calls from Zoom by entering the wrong values in the JWT token or Secret token or by removing the application created in Zoom.

Is there a limit to the number of calls that can be performed towards the Zoom endpoint?

Rate limits depend on the account plan: Pro or Business+ (Business, Education, Enterprise & Partners).

Currently, the connector does not allow limiting the number of calls performed towards the Zoom API endpoint. In upcoming releases, the Nexthink web interface will provide the ability to cap the number of requests and show when the limit has been reached.

To learn more about rate limits, visit Zoom Developers website.

Last updated