choose-zoom-approach
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseChoose Zoom Approach
选择Zoom方案
Pick the smallest correct Zoom surface for the job, then layer in only the supporting pieces that are actually required.
为当前需求选择最轻量化的适用Zoom接入层，之后仅叠加实际需要的支持组件。
Decision Framework
决策框架
| Problem Type | Primary Zoom Surface |
|---|---|
| Deterministic backend automation, account management, reporting, scheduled jobs | rest-api |
| Event delivery to your backend | webhooks or websockets |
| Embed Zoom meetings into your app | meeting-sdk |
| Build a fully custom video experience | video-sdk |
| Build inside the Zoom client | zoom-apps-sdk |
| AI-agent tool workflows over Zoom data | zoom-mcp |
| Real-time media extraction or meeting bots | rtms plus meeting-sdk when needed |
| Phone workflows | phone |
| Contact Center or Virtual Agent flows | contact-center or virtual-agent |
| 问题类型 | 首选Zoom接入层 |
|---|---|
| 确定性后端自动化、账号管理、报表、定时任务 | rest-api |
| 向你的后端推送事件 | webhooks 或 websockets |
| 将Zoom会议嵌入到你的应用中 | meeting-sdk |
| 构建完全自定义的视频体验 | video-sdk |
| 在Zoom客户端内部开发功能 | zoom-apps-sdk |
| 基于Zoom数据的AI Agent工具工作流 | zoom-mcp |
| 实时媒体提取或会议机器人 | rtms，需要时搭配 meeting-sdk |
| 电话相关工作流 | phone |
| 联络中心或虚拟Agent流程 | contact-center 或 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 when the user needs both stable system actions and AI-driven discovery.
rest-api + zoom-mcp
- 当用户实际需要Zoom会议语义时，请勿推荐Video SDK
- 当用户需要完全自定义的会话产品时，请勿推荐Meeting SDK
- 不要仅使用MCP方案替代确定性后端自动化
- 当用户同时需要稳定的系统操作和AI驱动的内容发现时，优先选择混合方案
rest-api + zoom-mcp
What To Produce
输出要求
- One recommended path
- Minimum supporting components
- Hard constraints and tradeoffs
- Immediate next implementation step
- 一条推荐路径
- 最少的支持组件
- 硬性约束和权衡点
- 可立即执行的下一步落地步骤