build-zoom-phone-integration
$
npx mdskill add anthropics/knowledge-work-plugins/build-zoom-phone-integrationIntegrate Zoom Phone via API, webhooks, or URI schemes.
- Enables call automation, CRM dialers, and analytics workflows.
- Connects to Zoom Phone APIs, webhooks, and Smart Embed events.
- Selects integration method based on user task requirements.
- Delivers results through automated calls, SMS, or web interactions.
SKILL.md
.github/skills/build-zoom-phone-integrationView on GitHub ↗
--- name: build-zoom-phone-integration description: "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." triggers: - "zoom phone" - "phone smart embed" - "zoom phone api" - "zoom phone webhook" - "call history" - "call handling" - "zoomphonecall" - "zoomphonesms" - "phone crm integration" - "call element" --- # /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](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](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](../contact-center/SKILL.md). ## Quick Links Start here: 1. [concepts/architecture-and-lifecycle.md](concepts/architecture-and-lifecycle.md) 2. [scenarios/high-level-scenarios.md](scenarios/high-level-scenarios.md) 3. [references/deprecations-and-migrations.md](references/deprecations-and-migrations.md) 4. [references/forum-top-questions.md](references/forum-top-questions.md) 5. [references/smart-embed-event-contract.md](references/smart-embed-event-contract.md) 6. [references/call-handling-patterns.md](references/call-handling-patterns.md) 7. [references/environment-variables.md](references/environment-variables.md) 8. [references/crm-sample-validation.md](references/crm-sample-validation.md) 9. [troubleshooting/common-issues.md](troubleshooting/common-issues.md) 10. [RUNBOOK.md](RUNBOOK.md) 11. [examples/smart-embed-postmessage-bridge.md](examples/smart-embed-postmessage-bridge.md) 12. [examples/phone-api-service-pattern.md](examples/phone-api-service-pattern.md) 13. [references/source-map.md](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`) 4. Capture real-time events (Smart Embed events and/or webhooks). 5. Persist call identifiers and correlate records (`call_id`, `call_history_uuid`, `call_element_id`). 6. Apply migration-safe data mapping (v1 -> v2 -> v3) and handle renamed fields. 7. 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](scenarios/high-level-scenarios.md) for details. ## Chaining - OAuth setup/token lifecycle: [../oauth/SKILL.md](../oauth/SKILL.md) - Phone and account resources via REST: [../rest-api/SKILL.md](../rest-api/SKILL.md) - Event delivery and signature validation: [../webhooks/SKILL.md](../webhooks/SKILL.md) - Contact Center blended journey: [../contact-center/SKILL.md](../contact-center/SKILL.md) ## Environment Variables - See [references/environment-variables.md](references/environment-variables.md) for standardized `.env` keys and where to find each value.
More from anthropics/knowledge-work-plugins
- accessibility-reviewRun a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", "check a11y", "is this accessible?", or when reviewing a design for color contrast, keyboard navigation, touch target size, or screen reader behavior before handoff.
- account-research"Research a company using Common Room data. Triggers on 'research [company]', 'tell me about [domain]', 'pull up signals for [account]', 'what's going on with [company]', or any account-level question."
- analyzeAnswer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.
- architectureCreate or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
- audit-supportSupport SOX 404 compliance with control testing methodology, sample selection, and documentation standards. Use when generating testing workpapers, selecting audit samples, classifying control deficiencies, or preparing for internal or external audits.
- brand-reviewReview content against your brand voice, style guide, and messaging pillars, flagging deviations by severity with specific before/after fixes. Use when checking a draft before it ships, when auditing copy for voice consistency and terminology, or when screening for unsubstantiated claims, missing disclaimers, and other legal flags.
- brand-voice-enforcement>
- briefGenerate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
- build-dashboardBuild an interactive HTML dashboard with charts, filters, and tables. Use when creating an executive overview with KPI cards, turning query results into a shareable self-contained report, building a team monitoring snapshot, or needing multiple charts with filters in one browser-openable file.
- build-zoom-botBuild a Zoom meeting bot, recorder, or real-time media workflow. Use when joining meetings programmatically, processing live media or transcripts, or combining Meeting SDK, RTMS, and backend services.