mcpField
B
build-zoom-phone-integration

build-zoom-phone-integration

github.com/anthropicsDevelopment33.6k2.1k installsUpdated 1d ago
Repository

About build-zoom-phone-integration

A reference skill for developers implementing Zoom Phone integrations through APIs, webhooks, Smart Embed, or URI launches. It covers lifecycle decisions, event and call-record handling, migration, and security guidance.

Key features

  1. 01Guidance for API, webhook, and embed workflows
  2. 02Click-to-dial and SMS URI patterns
  3. 03Real-time event capture
  4. 04Call record correlation and migration
  5. 05Security and OAuth setup guidance

Use cases

  1. 01Adding a softphone pane to a CRM
  2. 02Launching calls from contact records
  3. 03Building a webhook-driven operations board
  4. 04Migrating call analytics to newer records

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/anthropics/knowledge-work-plugins --skill build-zoom-phone-integration

After installing, type/build-zoom-phone-integrationin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

RUNBOOK.md
concepts/
architecture-and-lifecycle.md
examples/
phone-api-service-pattern.md
smart-embed-postmessage-bridge.md
references/
call-handling-patterns.md
crm-sample-validation.md
deprecations-and-migrations.md
environment-variables.md
forum-top-questions.md
smart-embed-event-contract.md
source-map.md
scenarios/
high-level-scenarios.md
troubleshooting/
common-issues.md

Details

From the project README

/build-zoom-phone-integration

Background reference for Zoom Phone integrations across API, webhook, Smart Embed, and URI-launch workflows.

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

Official docs:

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).

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

Comments

Markdown supported