This topic was automatically generated from Slack. You can find the original thread here.
Hi guys, I have a problem with custom OAuth Client for Zoom Admin application
When I am trying to use any scopes other than user:read:user:admin I get error with Invalid Scopes, despite the fact that they’re actually the same as in my Zoom application (currently it’s development app)
The only way for me to actually use my OAuth Client is to leave Pipedream scopes empty - in this case I can pass authentication with proper scopes, but then it cannot authenticate my requests to Zoom or setup Webhook connection via Pipedream (Invalid Scopes)
FYI: I am in Poland, so I cannot test actual Zoom Admin connection without using VPN (it’s US only)
Hey , on Pipedream side, you can left the Pipedream scopes blank, it will still work. Actually it is how Pipedream Official OAuth client for Zoom Admin is setup
I tested that, but I don’t receive any events I am working with meeting.ended and webinar.ended webhook events
but when I setup webhook URL directly inside Zoom App I get every expected event, and on top of that I think that when I deploy the trigger in PD, I should see PD webhook URL inside my Zoom app - in the same section, or am I missing something?
when I deploy the trigger in PD, I should see PD webhook URL inside my Zoom app
That should be expected, but some apps might not showing it based on my experience.
For your Pipedream source that’s not emitting event, could you share your Pipedream source log (maybe via DM) so I can check further?
Unfortunately there are a few apps in Pipedream whose triggers do not work with custom OAuth clients, and Zoom is one of those apps: OAuth Clients - Pipedream
Right, but since Zoom (including Zoom Admin) require that you register 1 single webhook with your OAuth app in their UI, Pipedream isn’t able to programmatically register webhook listeners on your behalf when you use your own OAuth client, so even though our UI lets you create an OAuth client, if you deploy triggers that use a connected account with that OAuth client, it’ll never emit events unfortunately. That’s a known gap right now.
Is fixing this gap on Pipedream’s roadmap? It would be really helpful to know if there are plans to address this limitation with custom OAuth clients for Zoom triggers. We’re conducting good part of our Business in Europe, so we can’t use default Pipedream Client without VPN and since we can’t have our own Zoom Client our customers won’t be able to setup any triggers
Are there any workarounds in the meantime?
It’s on the roadmap, yes, but I don’t have an eta for you, since it’s a bit complex. Are you using this in the Pipedream workflow builder or via Pipedream Connect?
I am working with 
and since we can’t have our own Zoom Client our customers won’t be able to setup any triggers