phone

Zoom Phone skill pack for OAuth, Phone APIs, webhooks, Smart Embed postMessage events, URI schemes, and call-history migration patterns. Use for CRM/CTI dialer workflows, real-time call tracking, and

SKILL.md

GitHub

Zoom Phone

Implementation guidance for Zoom Phone integrations across API, webhook/event, Smart Embed, and URI-launch workflows.

Official docs:

The current API Hub inventory contains 391 Phone operations (verified 2026-07-10), including expanded call-handling/settings coverage and call-element recording/voicemail resources. Use the generated Phone API reference for exact paths rather than relying on an older endpoint list in examples.

Routing Guardrail

Quick Links

Start here:

  1. concepts/architecture-and-lifecycle.md
  2. scenarios/high-level-scenarios.md
  3. references/deprecations-and-migrations.md
  4. references/forum-top-questions.md
  5. references/smart-embed-event-contract.md
  6. references/call-handling-patterns.md
  7. references/environment-variables.md
  8. references/crm-sample-validation.md
  9. troubleshooting/common-issues.md
  10. RUNBOOK.md
  11. examples/smart-embed-postmessage-bridge.md
  12. examples/phone-api-service-pattern.md
  13. references/source-map.md

Common Lifecycle Pattern

  1. Provision account prerequisites (Zoom Phone license, admin setup, SMS readiness).
  2. Create OAuth app and scopes in Marketplace.
  3. Choose integration surface:
  • Smart Embed (iframe + postMessage)
  • REST + webhooks
  • URI launch (callto, tel, zoomphonecall, zoomphonesms)
  1. Capture real-time events (Smart Embed events and/or webhooks).
  2. Persist call identifiers and correlate records (call_id, call_history_uuid, call_element_id).
  3. Apply migration-safe data mapping (v1 -> v2 -> v3) and handle renamed fields.
  4. Harden security (origin validation, webhook signature validation, least-privilege scopes).

Need to create/configure the Marketplace app first? Use Marketplace app management for General App or S2S app setup, admin/user scope selection, event subscription behavior, and credential response shapes before implementing Phone APIs or Smart Embed workflows. Start from the General App Phone template or S2S Phone template.

High-Level Scenarios

  • CRM softphone pane using Smart Embed + contact search/match callbacks.
  • Click-to-call from account/contact table via zp-make-call.
  • Call disposition workflow using zp-save-log-event and custom notes page.
  • SMS engagement workflow with zoomphonesms:// and zp-sms-log-event.
  • Real-time operational board driven by phone.* webhook events.
  • Call analytics migration from legacy call logs to call history/call elements.
  • Admin automation for user/auto-receptionist/call-queue call-handling settings.

See scenarios/high-level-scenarios.md for details.

Chaining

Environment Variables