build-zoom-contact-center-app — Claude command: Zoom Contact Center
Walks the agent through recon, a written plan, scoped edits and verification when a repo needs Zoom Contact Center integration.
~/.codex/prompts/build-zoom-contact-center-app.mdWhat build-zoom-contact-center-app does
Reach for this command when the repo needs Zoom Contact Center work on web, mobile or the backend. It starts with recon: the agent inspects existing Contact Center code, SDK usage, OAuth handling and event consumers. Then it pins down the target platform and workflow — web embed, native wrapper, engagement handling, campaign flow or backend orchestration.
Before touching files, the command demands a plan: state the platform and workflow, list the files to change, describe the auth path, the event path and the interaction model, and say how the first pass will be verified. Edits come after that, at the proper platform layer, reusing the app's existing structure instead of generic abstractions. The first pass stays scoped to one engagement or routing workflow. Secrets and account identifiers stay out of the output.
Verification closes the loop: the agent re-reads the changed integration files and supporting auth or event code, runs a local build or tests where available, and checks the handler shape. Missing SDK setup, app configuration or account prerequisites get reported as blockers rather than papered over. In Claude the command file lives at ~/.codex/prompts/build-zoom-contact-center-app.md.
What it helps with
- audit existing Contact Center code before editing
- pick the right platform layer: web, mobile or backend
- spell out the auth and event paths before writing code
- keep the first pass to a single engagement workflow
- verify the build and handler shape after changes
Example prompts for the agent
- build-zoom-contact-center-app: add a web embed for Contact Center to this repo
- build-zoom-contact-center-app: we need campaign event handling on the backend
- build-zoom-contact-center-app: review the current integration and list what's missing
How to install build-zoom-contact-center-app
Manually: put the files in place
~/.codex/prompts/build-zoom-contact-center-app.mdCall it with /prompts:build-zoom-contact-center-app. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.claude/commands/build-zoom-contact-center-app.mdCall it with /build-zoom-contact-center-app. For all projects use ~/.claude/commands/
Manually: put the files in place
.github/prompts/build-zoom-contact-center-app.prompt.mdManually: put the files in place
.gemini/commands/build-zoom-contact-center-app.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about build-zoom-contact-center-app
How do I install build-zoom-contact-center-app in Claude?
Place the command file at ~/.codex/prompts/build-zoom-contact-center-app.md — there is no separate install command.
What does build-zoom-contact-center-app do?
It drives the agent through recon, planning, scoped edits and verification for a Zoom Contact Center integration on web, mobile or backend.
What does the command need to work?
SDK setup, app configuration and Zoom account prerequisites. When any of those are missing, the agent names the blocker in its summary.
Source text
build-zoom-contact-center-app.md · MIT
--- description: Implement a Zoom Contact Center integration for web, mobile, or backend workflows with the right auth and event handling. --- # Build Zoom Contact Center App Use this command when the repo needs Zoom Contact Center web, mobile, or backend integration work. ## Preflight 1. Inspect the codebase for existing Contact Center code, SDK usage, OAuth handling, and event consumers. 2. Identify the target platform and workflow: web embed, native wrapper, engagement handling, campaign flow, or backend orchestration. 3. Confirm the owning runtime and UI surface. 4. Check for the required auth, SDK, or endpoint configuration without printing secrets. ## Plan Before making changes: - state the target platform and Contact Center workflow - list the files that will be changed - state the auth path, event path, and interaction model - state how the initial integration will be verified ## Commands 1. Add or correct the Contact Center integration at the proper platform layer. 2. Reuse existing app structure and avoid generic abstractions that hide platform-specific requirements. 3. Keep the first pass scoped to one concrete engagement or routing workflow. 4. Add the minimum auth, event, and UI wiring required for a working path. 5. Keep secrets and account-specific identifiers out of output. ## Verification 1. Re-read the platform integration files and supporting auth or event code that changed. 2. Run local build or tests where available. 3. Verify the configured workflow path and handler shape. 4. State any remaining blocker such as missing SDK setup, app configuration, or account prerequisites. ## Summary ```text ## Result - Action: implemented or updated a Zoom Contact Center workflow - Status: success | partial | failed - Details: platform, files changed, auth path, verification run ``` ## Next Steps - Test the target engagement flow in the intended environment. - Expand to more event or campaign cases only after the base path works. - If auth or delivery is failing, use the narrower setup or debug commands next.
© Zoom · MIT · openai/plugins
