Zoom OAuth Planning in Codex for a Test Web App
Scope a Zoom OAuth flow from who authorizes it, the actions needed, and how configuration and refresh are handled.
中文Setup for Codex (Zoom plugin)
Use the full Zoom Codex plugin. The example needs only fictional account details. A live test requires a developer app and a designated test account.
- In Codex, open /plugins and install Zoom. Use the full plugin package so its sibling skills and references are available.
- Invoke the bundled skill as $setup-zoom-oauth in a scratch workspace. Keep the example on the local or demo inputs described below.
Example task
Invoke $setup-zoom-oauth with: Each event organizer connects their own account to a scheduling portal. The pilot only reads meeting information. Produce an actor-to-grant decision, scope checklist, and a token lifecycle diagram using placeholders and current docs.Expected result
The design identifies a user-authorized flow, calls for verifying the exact read permissions, and keeps credential storage and refresh on the backend. No sample token or account information is needed.
Upstream documentation
Original SKILL.md on GitHub · MIT license · Source reviewed
Frequently asked question
Where do I verify the names of the required scopes?
Use the scope documentation for the exact API action and check the test app's configured scopes in the Zoom developer console.