API event
meeting.summary_completed — Zoom Meetings webhook reference.
Description
We are testing a private, user-managed General OAuth app in Development with a Make custom webhook. The app is installed and Authorized in the host’s Zoom My Library.
Scopes: meeting:read:summary and user:read:user.
What works:
- AI Companion generates the synthetic meeting summaries.
- The custom app successfully retrieves summaries through the REST API (HTTP 200).
- A direct synthetic JSON POST to the Make receiver returns HTTP 200 and is captured immediately.
Error / observed behavior
No Zoom request was observed at the receiver during the test window. We have not established a Zoom service fault or a Make plan limitation.
How to reproduce
- Enable Development Event Subscription and save “Meeting summary has been completed” with the Make HTTPS endpoint.
- Reauthorize the existing custom app connection after saving the subscription.
- Start Make’s webhook learning mode, which captures a request without running downstream actions.
- Host and end a new solo synthetic meeting as the authorized user, with AI Companion summary enabled.
- Confirm the summary exists. In our latest test, no new request appeared at Make through approximately 2 minutes 11 seconds after meeting end. Longer delivery delays are not ruled out.
- Restore the temporary subscription to off after the test.
Questions
- Are there additional prerequisites or restrictions for this event with a user-managed General app in Development, including solo meetings or summaries stored in Zoom Docs?
- Does this Development endpoint require CRC validation? Its editor permits Save and shows no Validate button; we observed no
endpoint.url_validationrequest. - Where can we see General app webhook delivery attempts? The Marketplace “Webhook Logs” tab is labeled “Webhook Only apps.”
- What processing/delivery window should we allow before treating a missing notification as a failed test?
We can provide app and test-meeting identifiers privately to Zoom staff for tracing.