I currently have a workflow set up where once a meeting ends, I get a webhook with the meeting information. I then filter the data of that webhook to include only our sales team members, then use GET to receive the meeting summary using the meeting UUID provided in the webhook.
This is successful 95% of the time. However the remaining 5% seems to be a mismatch in the reported UUID from the webhook, and the ‘real’ UUID (which I have not found).
In these instances, when I send the GET request to https://api.zoom.us/v2/meetings/{meeting_uuid}/meeting_summary , I get the error “Meeting does not exist". However, when viewing via the UI I can confirm a) the meeting happened b) there is a meeting summary and c) the host confirms they received the meeting summary via email.
This doesn’t seem to be a timing issue - I’ve tried over 24h after the meeting was held and get the same result.
I can confirm the meeting UUID is being appropriately encoded in the URL, and cannot seem to find a reason why only a small portion of these calls do not work, where as all the others do.
Is there another step I should be adding here: perhaps trying to get the meeting first and then hoping the correct meeting summary UUID will be provided that I can retrieve another way?
Hi @Lizosaurus , can you confirm the pre-requisite conditions have been met? You may not have the permission to access the meeting information or may not have the right meeting uuid. Please look into this and let me know
Yes, I can confirm.
Also verified by the fact I can retrieve other meetings of the same type by this user, and other users. I am using the meeting UUID as provided by Zoom’s webhook so, I don’t know what other UUID I should be using?
Hi @gianni.zoom thank you for this. However how can I tell if this is the case from the user’s UI? E.g. how can I ensure they turn on the meeting summary and not just AI companion?
@gianni.zoom I can confirm it is enabled, and the user notes it has been. Their other calls are working as expected - just two calls from this one client not working. It’s bizarre.
The last error I thought was the same issue, turned out to be a different one – so far I only have one report of this exact issue. So I think maybe it was a one off… will let you know if that changes!
