choose-zoom-approach

Original：🇺🇸 English
Translated

Choose the right Zoom architecture for a use case. Use when deciding between REST API, Webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Zoom MCP, Phone, Contact Center, or a hybrid approach.

3installs
Sourceanthropics/knowledge-work-plugins
Added on

NPX Install

npx skill4agent add anthropics/knowledge-work-plugins choose-zoom-approach

Tags

Translated version includes tags in frontmatter
zoom-developmentarchitecture-selectionapi-guidancesdk-integrationsolution-design

SKILL.md Content

View Translation Comparison →

Choose Zoom Approach

Pick the smallest correct Zoom surface for the job, then layer in only the supporting pieces that are actually required.

Decision Framework

Problem TypePrimary Zoom Surface
Deterministic backend automation, account management, reporting, scheduled jobsrest-api
Event delivery to your backendwebhooks or websockets
Embed Zoom meetings into your appmeeting-sdk
Build a fully custom video experiencevideo-sdk
Build inside the Zoom clientzoom-apps-sdk
AI-agent tool workflows over Zoom datazoom-mcp
Real-time media extraction or meeting botsrtms plus meeting-sdk when needed
Phone workflowsphone
Contact Center or Virtual Agent flowscontact-center or virtual-agent

Guardrails

  • Do not recommend Video SDK when the user actually needs Zoom meeting semantics.
  • Do not recommend Meeting SDK when the user needs a fully custom session product.
  • Do not replace deterministic backend automation with MCP-only guidance.
  • Prefer hybrid 
    rest-api + zoom-mcp
    when the user needs both stable system actions and AI-driven discovery.

What To Produce

  • One recommended path
  • Minimum supporting components
  • Hard constraints and tradeoffs
  • Immediate next implementation step