$ ~/registry/skill/anthropics-partner-built-zoom-plugin-skills-phone

SKILL

build-zoom-phone-integration

Name: build-zoom-phone-integration
Author: anthropics

Build Zoom Phone integrations, call workflows, and telephony automation features.

Stars

★ 22,528

Source

GitHub

Updated

2026-07-11

// securityCaution

Prompt only, no code
Open source

Summary

Overall this is a prompt-only, open-source reference skill with no keys, remote endpoints, or local execution capability, so the baseline risk is low. The main caution is that it guides Zoom Phone OAuth, webhooks, and API integrations, which are normal integration surfaces and should be implemented with least privilege and callback validation.

CredentialsLow risk

The material explicitly states no keys or environment variables are required; there is no sign of credential collection, forwarding, or abuse.

Network egressLow risk

No remote endpoint host is declared, and the content is reference documentation; there is no sign of user data being exfiltrated to unknown destinations.

Code executionLow risk

System checks mark it as prompt-only, with no process spawning, code execution, or local system capability usage.

Data accessCaution

It guides handling call records, events, CRM/CTI-related data, and webhook callbacks, but this is within normal Zoom Phone integration scope and no overbroad access is described.

Supply chainCaution

The source is GitHub and marked open-source, so it is auditable; however, the license is undeclared, community adoption is 0 stars, and maintenance status is unknown, so supply-chain confidence is only moderate.

Recommendations

Use least-privilege Zoom OAuth scopes and verify webhook signatures and source domains.
Do not send call records, contacts, or CRM data to unnecessary third-party services.
When integrating Smart Embed or URI schemes, restrict acceptable origins and callback parameters.
Before deployment, verify the repository license, maintenance activity, and dependency list.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "build-zoom-phone-integration" skill from askskill:
1. Download https://raw.githubusercontent.com/anthropics/knowledge-work-plugins/main/partner-built/zoom-plugin/skills/phone/SKILL.md
2. Save it as ~/.claude/skills/phone/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// examples

Implement OAuth and Phone API integration

Prompt

Design an implementation plan for a Zoom Phone integration, including the OAuth flow, access token retrieval, Phone API calls for user extensions and call logs, plus Node.js sample code and security considerations.

Expected

A complete integration plan with auth flow details, API steps, sample code, and security guidance.

Automate inbound call handling with webhooks

Prompt

Design a webhook automation flow for Zoom Phone inbound calls: when a call event arrives, look up CRM customer data, route by customer tier to different agents, and record the outcome. Provide a flow outline, pseudocode, and retry strategy.

Expected

An inbound event handling design including routing logic, CRM integration, pseudocode, and failure handling recommendations.

Embed a CRM dialer

Prompt

Explain how to integrate a Zoom Phone CTI/dialer into a CRM with click-to-dial, call status sync, screen pops, and URI scheme launching, and provide frontend integration steps and a testing checklist.

Expected

A CRM dialer integration guide covering feature design, frontend implementation, and test checkpoints.

// docs

/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:

https://developers.zoom.us/docs/phone/
CRM sample reference: https://github.com/zoom/CRM-Sample

Routing Guardrail

If the user needs embedded softphone behavior in a web app, use Smart Embed (examples/smart-embed-postmessage-bridge.md).
If the user needs call records, analytics, or automation, use Phone REST API and webhooks (references/deprecations-and-migrations.md).
If the user needs click-to-dial/SMS launch from external UI, use URI schemes (zoomphonecall://, zoomphonesms://).
If the user mixes Zoom Phone and Contact Center, chain with ../contact-center/SKILL.md.

Quick Links

Start here:

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

Common Lifecycle Pattern

Provision account prerequisites (Zoom Phone license, admin setup, SMS readiness).
Create OAuth app and scopes in Marketplace.
Choose integration surface:

Smart Embed (iframe + postMessage)
REST + webhooks
URI launch (callto, tel, zoomphonecall, zoomphonesms)

Capture real-time events (Smart Embed events and/or webhooks).
Persist call identifiers and correlate records (call_id, call_history_uuid, call_element_id).
Apply migration-safe data mapping (v1 -> v2 -> v3) and handle renamed fields.
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

OAuth setup/token lifecycle: ../oauth/SKILL.md
Phone and account resources via REST: ../rest-api/SKILL.md
Event delivery and signature validation: ../webhooks/SKILL.md
Contact Center blended journey: ../contact-center/SKILL.md

Environment Variables

See references/environment-variables.md for standardized .env keys and where to find each value.

Configure Zoom webhooks for subscriptions, signature checks, event handling, and retries.

anthropicsGet→

$ loading_