build-zoom-phone-integration — Claude command: Zoom Phone integration
A Claude command that walks the agent through preflight, planning and verification while building a Zoom Phone integration: APIs, Smart Embed, calling flows, events.
~/.codex/prompts/build-zoom-phone-integration.mdWhat build-zoom-phone-integration does
Reach for this command when a repo needs Zoom Phone APIs, an embedded phone experience, CTI-style workflows or call automation. The agent starts by inspecting the codebase: existing phone integration code, OAuth handling, embed surfaces, event consumers. Then it works out which path applies — Smart Embed, direct API usage, call automation or a CRM integration.
Before touching files, the command asks for a plan: the phone workflow being implemented, the files to change, the auth path, the event path and the user interaction surface, plus how the first flow will be verified. After that the agent adds or corrects the integration at the right UI or backend layer and reuses existing routing and API abstractions where it can. The first pass stays on one concrete calling or phone-data workflow.
Verification is stepwise: re-read the changed integration and auth code, run a local build or tests, check the shape of the API, embed or event path. The command also asks you to name remaining blockers — missing account setup, OAuth scope gaps, runtime prerequisites. When auth is incomplete, it points you at /setup-zoom-oauth.
What it helps with
- add a Zoom Phone API integration to a repo
- embed the Smart Embed phone surface in an existing UI
- wire a CTI-style calling flow with event handling
- reuse existing routing and API abstractions instead of new ones
- surface blockers like OAuth scope gaps before release
Example prompts for the agent
- implement a Zoom Phone integration in this repo
- add Smart Embed and call event handling
- build one working calling flow and verify it locally
How to install build-zoom-phone-integration
Manually: put the files in place
~/.codex/prompts/build-zoom-phone-integration.mdCall it with /prompts:build-zoom-phone-integration. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.claude/commands/build-zoom-phone-integration.mdCall it with /build-zoom-phone-integration. For all projects use ~/.claude/commands/
Manually: put the files in place
.github/prompts/build-zoom-phone-integration.prompt.mdManually: put the files in place
.gemini/commands/build-zoom-phone-integration.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about build-zoom-phone-integration
How do I install build-zoom-phone-integration in Claude?
Place the prompt file at ~/.codex/prompts/build-zoom-phone-integration.md.
What does build-zoom-phone-integration do?
It guides the agent through codebase inspection, planning, edits and verification while building a Zoom Phone integration covering APIs, Smart Embed, calling flows and events.
What do I need before running it?
Working Zoom auth and event configuration. If OAuth is incomplete, the command points you at /setup-zoom-oauth.
Source text
build-zoom-phone-integration.md · MIT
--- description: Implement a Zoom Phone integration around APIs, Smart Embed, calling flows, and event handling. --- # Build Zoom Phone Integration Use this command when the repo needs Zoom Phone APIs, embedded phone experiences, CTI-style workflows, or call-related automation. ## Preflight 1. Inspect the codebase for existing phone integration code, OAuth handling, embed surfaces, and event consumers. 2. Identify whether the workflow is Smart Embed, direct API usage, call automation, CRM integration, or another phone-specific path. 3. Confirm the runtime and UI surface that will own the phone workflow. 4. Check for the required auth and event configuration without printing secrets. ## Plan Before making changes: - state the Phone workflow being implemented - list the files that will be changed - state the auth path, event path, and user interaction surface - state how the initial phone flow will be verified ## Commands 1. Add or correct the Zoom Phone integration at the appropriate UI or backend layer. 2. Reuse existing routing, event, and API abstractions where possible. 3. Keep the first pass focused on one concrete calling or phone-data workflow. 4. Add the minimum configuration, auth handling, and event logic required for a working path. 5. Avoid blending general meeting assumptions into phone-specific workflows. ## Verification 1. Re-read the phone integration code and supporting auth or event code that changed. 2. Run local build or tests where available. 3. Verify the API, embed, or event path shape. 4. State any remaining blocker such as missing account setup, OAuth scope gaps, or runtime prerequisites. ## Summary ```text ## Result - Action: implemented or updated a Zoom Phone integration - Status: success | partial | failed - Details: files changed, auth path, event path, verification run ``` ## Next Steps - Exercise one real call-related workflow end to end. - Add CRM or analytics follow-up only after the base integration works. - If auth is incomplete, run `/setup-zoom-oauth`.
© Zoom · MIT · openai/plugins