Hi,

It sounds like you are using Webhook By Zapier as an action to send custom http reqeusts.

As far as I know, this action itself does not deal with authentication and is typically reliant on a webhook endpiont that takes a static key or secret.

If you have already registered your own app to have some clientId and secret, perhaps you can check out the JWT authentication flow: https://developers.ringcentral.com/guide/authentication/jwt/quick-start.

The reason I recommend this is that you can repeatedly use the same JWT in exchange of a valid token. You can set up a multi-step zap that would always use the JWT to get a new access token, then use that access token to call the RC Platform API. You can reach out to our dev support if you’re running into issues with those requests.

It does mean that if the JWT is stolen with the clientId and secret, then anyone could use it to gain access to your account though. Make sure they are kept safe. Also, depending on your needs, you could create an extension that has limited access to create this JWT instead of using your super admins. When you register your app, it’s also recommended to only declare access to the feature you need specifically for this to limit the damage if these credentials leak.

Hope that helps!

I finally ended up hiring someone to do it.  I don’t know what black magic he used, but it works!

Unfortunately Ring Central Support never even replied.  I sent two tickets and didn’t get any response, so I’m guessing they don’t know the answer.