build-zoom-phone-integration
Reference skill for Zoom Phone. Use after routing to a phone workflow when implementing OAuth, Phone APIs, webhooks, Smart Embed events, URI schemes, CRM or CTI dialers, or call handling automation.
Security Assessment
About build-zoom-phone-integration
This reference skill covers building Zoom Phone integrations across REST APIs, webhooks, Smart Embed (embedded softphone), and URI-launch workflows. It helps developers implement CRM/CTI dialers, call-handling automation, click-to-dial and SMS launch, and call-record analytics by routing them to the correct integration surface and documenting the lifecycle for each.
The skill provides architecture and lifecycle guidance, high-level scenarios (CRM softphone panes, click-to-call, call disposition logging, SMS engagement, real-time operational boards, and legacy-to-current call-log migration), call-handling API patterns, Smart Embed postMessage event contracts, environment-variable references, and troubleshooting. It documents endpoint families for call-handling settings, a migration-safe call-history service pattern that normalizes v2/v3 payload shapes, and URI schemes such as `zoomphonecall://` and `zoomphonesms://`. Its security guidance is defensive: keep OAuth tokens on the server only, validate Smart Embed origins, verify webhook signatures, and use least-privilege scopes.
It targets developers embedding softphone behavior in web apps or wiring Zoom Phone call data into CRM and analytics systems. The content is documentation and code-pattern reference grounded in official Zoom Phone docs and the Zoom CRM sample, not standalone executable tooling.
FAQ
What integration surfaces does it cover?
Smart Embed (iframe + postMessage softphone), Phone REST API and webhooks for call records/automation, and URI schemes (`zoomphonecall://`, `zoomphonesms://`) for click-to-dial/SMS launch.
How are credentials handled securely?
OAuth tokens are kept on the server only; the skill emphasizes origin validation for Smart Embed, webhook signature validation, and least-privilege scopes.
How does it handle API version drift?
It recommends a single adapter layer that normalizes inbound payloads, centralized versioned endpoint constants, and feature-flagged optional fields; the sample service normalizes v2/v3 call-history shapes.
What are the prerequisites?
A Zoom Phone license and admin setup, an OAuth app with appropriate scopes in the Zoom Marketplace, and optionally SMS enablement.
Is this executable tooling?
No. It is a documentation and pattern reference for Zoom Phone, grounded in the official docs and the Zoom CRM-Sample repository.
All Files
14 filesInstall build-zoom-phone-integration
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
anthropics/knowledge-work-plugins