# General OAuth Development app: meeting.summary\_completed not received despite generated summary

**URL:** <https://devforum.zoom.us/t/general-oauth-development-app-meeting-summary-completed-not-received-despite-generated-summary/146465>\
**Category:** API and Webhooks\
**Created:** [September 14, 2026, 11:46pm UTC](https://devforum.zoom.us/t/general-oauth-development-app-meeting-summary-completed-not-received-despite-generated-summary/146465 "2026-09-14T23:46:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![krissheldrake](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/krissheldrake/32/76645_2.png) [@krissheldrake](https://devforum.zoom.us/u/krissheldrake)\
**Post date:** [September 14, 2026, 11:46pm UTC](https://devforum.zoom.us/t/general-oauth-development-app-meeting-summary-completed-not-received-despite-generated-summary/146465/1 "2026-09-14T23:46:05Z")

</div>

### API event

`meeting.summary_completed` — [Zoom Meetings webhook reference](https://developers.zoom.us/docs/api/meetings/events/).

### 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

1. Enable Development Event Subscription and save “Meeting summary has been completed” with the Make HTTPS endpoint.
2. Reauthorize the existing custom app connection after saving the subscription.
3. Start Make’s webhook learning mode, which captures a request without running downstream actions.
4. Host and end a new solo synthetic meeting as the authorized user, with AI Companion summary enabled.
5. 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.
6. 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_validation` request.
- 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.
