build-zoom-meeting-app — Codex command: what it does, install
This command builds an embedded or managed Zoom Meeting flow in the current codebase. Use it when the project needs Meeting SDK setup, authentication, and a join path.
~/.codex/prompts/build-zoom-meeting-app.mdWhat build-zoom-meeting-app does
The command inspects the repository, frontend framework, backend support, and existing auth handling. It identifies the target platform and checks that the requirement is a real Zoom meeting rather than a custom media flow that belongs to Video SDK.
Before editing, the agent states the SDK surface, files to change, join or start path, backend requirements, and local verification plan. It then adds Meeting SDK initialization, the meeting entry call, the smallest required UI, environment wiring, and server-side auth support.
It rereads changed client and auth code, runs the relevant local build or tests, and checks that the UI reaches the expected join or start call. A server token or signature path is required for the auth flow, so missing credentials or callback setup can block completion.
What it helps with
- embed a Zoom meeting in the existing UI
- configure a meeting join or start flow
- add server-side token or signature support
- verify the meeting entry path locally
Example prompts for the agent
- Run
/build-zoom-meeting-appand add a Zoom meeting flow to the current project. - Check whether this needs Meeting SDK or Video SDK, then plan the required changes with
/build-zoom-meeting-app. - Set up the auth path and verify the local join call using
/build-zoom-meeting-app.
How to install build-zoom-meeting-app
Manually: put the files in place
~/.codex/prompts/build-zoom-meeting-app.mdCall it with /prompts:build-zoom-meeting-app. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.claude/commands/build-zoom-meeting-app.mdCall it with /build-zoom-meeting-app. For all projects use ~/.claude/commands/
Manually: put the files in place
.github/prompts/build-zoom-meeting-app.prompt.mdManually: put the files in place
.gemini/commands/build-zoom-meeting-app.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about build-zoom-meeting-app
How do I install build-zoom-meeting-app in Codex?
Copy the command file to ~/.codex/prompts/build-zoom-meeting-app.md.
What does build-zoom-meeting-app do?
It implements or updates a Zoom Meeting flow in the current codebase, including Meeting SDK setup, joining or starting a meeting, and server-side authentication.
What does the command need to work?
The project needs the appropriate Meeting SDK surface and a server-side token or signature path. The command also checks credentials, callbacks, domain configuration, and SDK prerequisites.
Source text
build-zoom-meeting-app.md · MIT
--- description: Implement an embedded or managed Zoom meeting flow in the current codebase with the right SDK and auth path. --- # Build Zoom Meeting App Use this command when the repo needs to embed or launch real Zoom meetings with the Meeting SDK or adjacent server-side join flow. ## Preflight 1. Inspect the codebase for existing Zoom meeting code, frontend framework, backend support, and auth handling. 2. Confirm the requested experience is a real Zoom meeting and not a custom video experience that belongs on Video SDK. 3. Identify the target platform: web, mobile, desktop, or multi-platform. 4. Check whether the codebase already has the required server-side token or signature path without printing secrets. ## Plan Before making changes: - state the target platform and Meeting SDK surface - list the files that will be changed - state the join or start flow, auth path, and required backend pieces - state how the meeting flow will be verified locally ## Commands 1. Inspect current app structure and place the meeting integration in the correct UI and server layers. 2. Add or correct Meeting SDK initialization, join or start flow, and backend auth support. 3. Keep the implementation aligned with the target platform’s established patterns instead of forcing a generic abstraction. 4. Add only the minimum UI, env wiring, and server code needed for a working meeting flow. 5. Keep secrets, tokens, and meeting credentials out of output and logs. ## Verification 1. Re-read the meeting client code and any server auth helpers that changed. 2. Run the relevant local build or tests. 3. Verify the UI path reaches the expected join or start call shape. 4. State any remaining blocker such as missing credentials, callback setup, domain config, or SDK prerequisites. ## Summary ```text ## Result - Action: implemented or updated a Zoom meeting app flow - Status: success | partial | failed - Details: platform, files changed, auth path, verification run ``` ## Next Steps - Test the join or start flow with a real meeting. - Add webhook or bot-side follow-up only if the product needs it. - If the requirement is actually custom media control, switch to `/build-zoom-video-sdk-app`.
© Zoom · MIT · openai/plugins
