1.7k Downloads
Overview
Headless Zoom integration that manages the full lifecycle of Zoom meetings (create, list, update, delete, inspect) via Zoom’s Server-to-Server OAuth API from within Clawdbot/CLI workflows.
Key Advantages
1.End-to-end meeting lifecycle management (create, list, update, delete, info) without opening the Zoom UI.
2.Enterprise-oriented Server-to-Server OAuth flow suitable for backend/bot automations.
3.Defaults to cloud recording, making it easy to ensure meetings are captured automatically.
4.Clean Node.js implementation that can be scripted or extended for custom workflows and integrations.
5.Headless, REST-based operation (Zoom API v2) for fast, non-browser automation.
Use Cases
- Automatically create Zoom meetings when a CRM deal reaches a certain stage or a ticket is created.
- Batch list and audit upcoming meetings for a particular account or team via CLI or bot commands.
- Update time, duration, or topic of scheduled Zoom meetings when calendar events shift.
- Retrieve meeting details for embedding into emails, chat notifications, or dashboards.
- Automatically delete obsolete or test meetings as part of cleanup or lifecycle policies in DevOps scripts.
Evaluation Scores
7.6
/ 10
Reliability
7.5
Functionality
7.8
Usability
7.2
Safety
7.0
Performance
8.5
Compatibility
8.0
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.6/103/19/2026▼
OS: darwin-arm64LLM: anthropic/claude-haiku-4.5
**Quick judgment:** Solid, focused Zoom meeting manager for backends and bots, well-suited to automated workflows inside Clawdbot or CI/CLI environments. It covers the key meeting lifecycle operations via Zoom’s REST API v2 and uses Server-to-Server OAuth for an enterprise-style, headless integration.
**What it’s good for:**
- Automating meeting creation, updates, and cleanup without touching the Zoom web UI.
- Integrating Zoom meeting operations into CRMs, ticketing systems, or custom Node.js/CLI tools.
- Ensuring meetings are recorded to the cloud by default as part of standardized workflows.
**Main risks & limitations:**
- Requires high-privilege Zoom scopes (admin/master meeting and recording permissions), so misconfiguration or secret leakage could expose meeting and recording data.
- Focused on meetings only; does not advertise support for advanced Zoom features (webinars, breakout configuration, complex user management, etc.).
- Operational reliability depends on correct Server-to-Server OAuth setup and safe handling of `ZOOM_CLIENT_ID`, `ZOOM_CLIENT_SECRET`, and `ZOOM_ACCOUNT_ID` environment variables.
**Recommended scenarios:**
Use this skill when you need scripted, repeatable control over Zoom meetings—from creation through deletion—inside automated backend processes, bots, or DevOps workflows, and you have the ability to manage Zoom server-to-server OAuth credentials securely. It is less suited to ad-hoc, non-technical users or environments where granting broad admin-level Zoom scopes is not acceptable.
Comments (0)
No comments yet. Be the first!