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.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 3.6w
- Forks
- 3.9k
01 前言 Front Matter
- name
- build-zoom-phone-integration
- triggers
- [ "zoom phone", "phone smart embed", "zoom phone api", "zoom phone webhook", "call history", "call handling", "zoomphonecall", "zoomphonesms", "phone crm integration", "call element" ]
- 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.
02 资源文件 13
- 参考文档concepts/architecture-and-lifecycle.md1.4 KB
- 参考文档examples/phone-api-service-pattern.md1.3 KB
- 参考文档examples/smart-embed-postmessage-bridge.md1.2 KB
- 参考文档references/call-handling-patterns.md961 B
- 参考文档references/crm-sample-validation.md1.4 KB
- 参考文档references/deprecations-and-migrations.md1.2 KB
- 参考文档references/environment-variables.md1.3 KB
- 参考文档references/forum-top-questions.md3.7 KB
- 参考文档references/smart-embed-event-contract.md1.0 KB
- 参考文档references/source-map.md888 B
- 参考文档RUNBOOK.md1.6 KB
- 参考文档scenarios/high-level-scenarios.md1.2 KB
- 参考文档troubleshooting/common-issues.md1.2 KB
03 SKILL.md 正文
/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-eventand custom notes page. - SMS engagement workflow with
zoomphonesms://andzp-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
.envkeys and where to find each value.
04 同仓库更多 Skills
ticket-deflector
Reads a forwarded customer email or ticket, pulls order and refund status from a payments connector (PayPal, Square, or Stripe) or Shopify, account history from the CRM, and open tickets from a support desk (Zoho Desk), drafts a tone-matched reply in the owner's writing voice, and can issue a refund through the payments connector with explicit owner approval. With Shopify connected it also runs a proactive order-triage mode that surfaces orders needing attention — unfulfilled past the promised window, payment problems, pending refunds, stuck shipments — and drafts the next action for each before the customer has to ask. Use when the user says "draft a response," "answer this customer," "where's my order," "I want a refund," "check my orders," or "anything about to blow up."
tax-season-organizer
Prepares tax-season materials for the owner's accountant, not tax advice. US federal tax; a non-US business gets its closed-books packet instead. Two modes: (1) quarterly estimated tax from YTD net income in the ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); (2) year-end 1099 prep, scanning the ledger, PayPal, and Stripe for contractors paid over USD 600 into a 1099-NEC list with missing W-9 flags. Any tax request routes first to /tax-prep, which confirms the books are closed and reconciled before running this skill. Use this skill directly only when the owner says the period's books are already closed: "books are closed, now do the 1099s," "run the quarterly estimate off the closed numbers," or "just the contractor W-9 list."
tax-prep
Prepares tax materials as a two-link chain — month-end-prep confirms the books are closed and reconciled first, then tax-season-organizer calculates the quarterly estimated payment or builds the year-end 1099-NEC list and accountant packet from those closed numbers. Requires a ledger (MYOB, NetSuite, QuickBooks, Xero, or Zoho Books); uses Gusto, PayPal, and Stripe when connected, else CSV upload. US federal tax math; a non-US business gets the closed-books packet. Prep material for a CPA, never tax advice, nothing filed. Trigger on "quarterly taxes," "estimated tax payment," "how much should I set aside," "1099s," "1099-NEC," "W-9s," "year-end tax prep," "get my books ready for my accountant," any phrasing that suggests a tax deadline is coming, or a question about net profit or YTD income that sounds like worry about a tax bill. An owner who says the period's books are already closed routes to tax-season-organizer directly.
speed-to-lead
Makes sure no inbound lead goes unanswered. Watches web forms, the shared inbox, and the CRM for new inquiries, qualifies each one against the owner's criteria, drafts a reply in the owner's voice with real meeting times for the owner to approve and send, routes anything hot to a human right away, and logs the whole thing to the CRM. Never sends on its own. Built to run on a schedule so overnight inquiries are drafted and sorted by morning, and works from forwarded or pasted inquiries when no connector is available. Use this whenever the owner is worried about inbound leads or response time — including phrasings like "leads are going cold," "did anyone answer that inquiry," "I keep missing form submissions," "nothing falls through the cracks," "handle my inbound," "respond to this lead," or "we lose people because nobody gets back fast enough." Reach for it for a single unanswered inquiry as readily as for a standing setup.
social-content-engine
Runs the owner's content operation as a standing thing rather than a one-off: keeps a rolling posting calendar, learns the owner's voice, generates on-brand Canva graphics, writes captions that sound like them, repurposes one asset into every channel format, and stages posts for approval instead of publishing on its own. Pulls product photos and prices from Shopify when connected; with no connectors, drafts the calendar and asset briefs for manual posting. Use this whenever the owner talks about posting, content, or social — including "I need to post more," "we've gone quiet on Instagram," "what should we post this month," "make the content," "give me a month of posts," "write this in my voice," "repurpose this," or "set up our content calendar." Reach for it for a single post as readily as for a full quarter. One handoff: a finished, approved campaign brief goes to canva-creator; this skill owns the standing operation.
smb-router
The front door to the Small Business plugin. Listens to what the owner needs right now — vague or specific — and routes them to the best skill or slash command for the moment. Also serves as a guide: explains what's available, suggests what to try next, and adapts recommendations based on stored business context. Trigger whenever the owner asks "what can you do," "help me with my business," "what should I focus on," "I don't know where to start," or any open-ended business request that doesn't clearly match a single skill.