I’ve got a workflow that listens when a recording is saved on our business Zoom account of which I’m the admin. In May it was working where the workflow would download the meeting to a Google Drive account and then delete the meeting recording.
Since our meetings started back up at the first of August, it doesn’t always delete the recording. It give a 401 or 404 error. If I personally record a meeting it will work, but it doesn’t work every time for the other accounts, even though I’m using the Zoom Admin control with my credentials.
Did something change in the api? do I need to do something to keep the authentication fresh?
Here’s the code I patterned it after:
I added the meetingId to the params and it seems to work better, but it still fails:
params: {
action: params.action,
meetingId: params.meetingId
},
@coderader would you mind clicking the Share button at the top-right of the workflow and share it with dylan@pipedream.com? I’d like to take a look at the specific errors to see if I can help you narrow down the issue.
@coderader Thanks for sharing. I made a small tweak to the last step that should give us more information on the error (Zoom returns error messages when they return e.g. 401 errors). The next time you observe a 404 or a 401 error, you should see any information they return as a part of the error now. If it’s not obvious what the error is from the message, let me know and I can help take a look.
So, I used the debugging that you helped with and the error. It presented that it said “This recording does not exist.” Then in the API I noticed this little phrase:
If a UUID starts with “/” or contains “//” (example: “/ajXp112QmuoKj4854875==”), you must double encode the UUID before making an API request.
So I tried to double encode the Meeting ID, but that didn’t seem to help.
Also, now some of the files are failing to upload to Google Drive because it’s returning “Unauthorized.”
@coderader you may want to reach out to Zoom re: the 401s. That step is failing trying to download the recording specifically, and it may be helpful to provide Zoom support specific URLs / access tokens (with the time when the request failed) to see what might be wrong. Unfortunately I don’t have any more debugging data that can tell me why the download might have failed, but I believe they’ll be able to help.