Zoom 401 forbidden error in Make.com Workflow

API and Webhooks
1

I am building a workflow in Make that downloads the recordings of meetings, audio, transcrips videos etc and then process it further.
The flow works fine but Sometime it works fine. But many times this flow stops with an error saying :
401 Forbidden invalid access token
I have no idea why this happens sometime. Previously when this happened, i simply created a new webhook and it worked fine. but why should I do it everytime? because of this I am losing a lot of imp meetings data… Need to know the reason behind.

I have reached out to Make team and this is there response on this: "I have tested and discussed the issue with the team. We don’t have much visibility on the error since it is originating directly from Zoom’s side. I recommend reaching out to Zoom support using the raw body of the request and response provided below.

{ “response”: { “status”: 401, “headers”: { “date”: “Wed, 19 Jun 2024 15:18:35 GMT”, “content-type”: “application/json;charset=UTF-8”, “transfer-encoding”: “chunked”, “connection”: “close”, “x-zm-trackingid”: “v=2.0;clid=us02;rid=WEB_9aecae15f60fc4e583159d4e09a0026e”, “x-content-type-options”: “nosniff”, “x-frame-options”: “SAMEORIGIN”, “cf-cache-status”: “DYNAMIC”, “set-cookie”: [ "_cf_bm=TYQSJc3IRjprh1r4zA6ZQEd2_CFsTPZio5zKsmQ[960-1718810315-1.0.1.1-pkudtQMX0A08GZb9qFp.2StlPTryDNTw3.OEmrASAkkYwrjQZWq]

2 
{
    "response": {
        "status": 401,
        "headers": {
            "date": "Wed, 19 Jun 2024 15:18:35 GMT",
            "content-type": "application/json;charset=UTF-8",
            "transfer-encoding": "chunked",
            "connection": "close",
            "x-zm-trackingid": "v=2.0;clid=us02;rid=WEB_9aecae15f60fc4e583159d4e09a0026e",
            "x-content-type-options": "nosniff",
            "x-frame-options": "SAMEORIGIN",
            "cf-cache-status": "DYNAMIC",
            "set-cookie": [
                "__cf_bm=TYQSJc3IRjprh1r4zA6ZQEd2_CFsTPZio5zKsmQ_960-1718810315-1.0.1.1-pkudtQMX0A08GZb9qFp.2StlPTryDNTw3.OEmrASAkkYwrjQZWq4Qgy0k0AdrXjEX4ydQhSnfTRXRutYIA3UZg; path=/; expires=Wed, 19-Jun-24 15:48:35 GMT; domain=.zoom.us; HttpOnly; Secure; SameSite=None"
            ],
            "report-to": "{\"endpoints\":[{\"url\":\"https:\\/\\/a.nel.cloudflare.com\\/report\\/v4?s=gELnuKEn6dhL3yc4WvCEuzT444JcHbIuaAF26as0PbjTv%2Bst8m1ZtXn0AB%2FIlvJZouRGbZWWE0Ghf5Mx05inJW8egiAmbpGjvBVGxbGSvC6lbD4jQvJSwEqCIatjCW5Nuw%3D%3D\"}],\"group\":\"cf-nel\",\"max_age\":604800}",
            "nel": "{\"success_fraction\":0.01,\"report_to\":\"cf-nel\",\"max_age\":604800}",
            "server": "cloudflare",
            "cf-ray": "89647e187ac30621-IAD",
            "alt-svc": "h3=\":443\"; ma=86400"
        },
        "body": {
            "status": false,
            "errorCode": 300,
            "errorMessage": "Forbidden"
        }
    },
    "request": {
        "url": 
        "headers": {
            "user-agent": "Make/production",
            "accept": "application/json",
            "authorization": "***"
        },
        "method": "GET"
    }
}
3

Screenshot 2024-06-19 200448|689x418
Screenshot 2024-06-19 234004|690x395

4

Hi @bisma
Thanks for reaching out to us and welcome to our Zoom Developer Community!
I am happy to take a look into this issue you are seeing for you. Can you please confirm if this is still happening to you?

5

I am having this very same issue. I have the automation split into two different paths and 1 path works, the other gives me the error code “[401] Forbidden”. It was working fine until October 21st.