According to the Zoom Apps FAQ:

Is my device eligible for Zoom Apps? Which devices can I use it on?

Zoom Apps require the Zoom desktop client for Windows and MacOS. Zoom Apps are not supported on mobile devices at this time.

When will Linux be supported for Zoom apps?

Thanks

-TAB

hello 

i am using Lenovo Chrome OS. and i installed the zoom app in it from playstore but in zoom i want to add another app. But i cant see an app tab in it. After some digging that i can use other app via zoom EMS but when i try to add zoom EMS i received 502 error. Any solutions for that.
"Lenovo Chrome Os is android."

Hi,

I've installed version 2.18.1 of Zoom for Lightning. However, when I receive an inbound call for an existing Lead record, the Lead Detail page does not pop up. This highly disrupts the sales process.

The softphone settings is set to "Single-matching record: Pop detail page".

Also, the incoming call screen only has the Caller Id and Dialed Number even though I've selected "If single Lead found, display: Name, Owner Name, Lead Status, Rating, Recommended Product Type".

See screenshot: https://share.zight.com/WnuWkq27

I've already confirmed that we are using the correct softphone layout.

Please advise.

Thanks in advance.

Despite the Aborb app being approved by admin (me), the app is not available to users in desktop client, nor does the app appear in the added apps list or apps on account list.

Hi smart people!

App is enabled for specific users.
Once noticed that the app was not available to the specified users, I added myself to the list of users approved for the app as well as a secondary test account.

-Neither my own account or the test account are able to access the app via the desktop client.
-Both my account and the test account are running the latest version of the client (6.2.3)
-Further, when the Absob app is searched for using the “add apps” feature in the client, no results are seen. (See provided screen capture)

Thank you in advance for any replies and thoughts/idea on what issue could be.

Hello,

I am trying to integrate Zoom Webhooks with an external server using the n8n platform to validate a URL in the event subscription section of the Zoom App Marketplace, but I am continuously experiencing an error in the URL validation process.

1. Problem Description:

-When entering the webhook URL into the event subscription form in Zoom App Marketplace, I receive the message: "Error in URL validation. Please try again later."

-The URL I am using is: https://n8n-n8n.ap5gnp.easypanel.host/webhook/{WEBHOOK_ID}.

-I have successfully tested this URL using Postman. The webhook responds with the correct token (plainToken and encryptedToken), but the Zoom platform still fails to validate the URL.

2. Steps Taken:

-I have configured a workflow in n8n that handles Zoom URL validation.
-I manually tested the webhook with Postman to ensure the webhook response is correct (I receive a 200 OK status code and the tokens in the expected format).
-I reviewed the Zoom Marketplace documentation, but I couldn’t find additional information to resolve the issue.

3. Technical Setup:

-I am using an external n8n server with the URL mentioned above.
-The webhook response is set to return the encrypted token as per Zoom’s URL validation specifications.

4. Expected Outcome:

-I would like to confirm if there are any additional restrictions for URL validation or if there could be an issue on Zoom’s end preventing the webhook validation.

Thank you for any guidance on this matter to help resolve this issue as soon as possible.

We are using Zoom as our phone system and have linked it to HubSpot.

We're dialing people through the Zoom app, which allows us to ring HubSpot contacts because they're pulled directly into the app.

We're having an issue where call activity is being logged against the wrong person/company or multiple contacts while we're forwarding a call.

According to HubSpot, the problem is in the integration.

How can we fix it?

Hello, this post is related to Zoom Workplace app on iOS. The documentation for setting SSO information is a bit confusing. For example,

Configuration Key = ForceSSOURl

So, it looks like value is "ForceSSOUrl=hooli", which doesn't work. Please clarify the documentation should be "hooli" instead of "ForceSSOUrl=hooli"