What is Server-to-Server OAuth and why use it?

Server-to-Server OAuth provides a secure, enterprise-grade authentication method that allows API access without a user context, ideal for automated workflows and headless integrations.

Which environment variables do I need and where do I get them?

You need ZOOM_CLIENT_ID, ZOOM_CLIENT_SECRET, and ZOOM_ACCOUNT_ID from the Zoom App Credentials tab after creating a Server-to-Server OAuth app.

Are there specific scopes required for this skill?

Yes. Required scopes include meeting read/write admin/master, user read admin, and recording read admin to view, create/update, and delete meetings and access recordings.

Zoom Manager

Scanned

@vnagin

npx machina-cli add skill @vnagin/zoom-manager-clawd --openclaw

Files (1)

SKILL.md

2.3 KB

Zoom Manager

Manage your Zoom meetings directly from Clawdbot with this powerful, headless integration. This skill allows you to automate your meeting workflows without ever opening the Zoom dashboard.

Key Features:

Full Meeting Lifecycle: Create, list, update, and delete meetings using simple natural language or CLI commands.
Enterprise-Ready: Built for Server-to-Server OAuth, ensuring secure and robust authentication.
Automated Recording: Default support for cloud recording to make sure your sessions are always captured.
Developer Friendly: Clean Node.js implementation that can be easily extended for custom automation flows (e.g., auto-scheduling after a CRM update).
Headless & Fast: No browser required; interacts directly with the Zoom REST API v2.

Setup

Create a Server-to-Server OAuth app in the Zoom App Marketplace.
Scopes Required: In the Zoom App Marketplace (Scopes tab), add the following:
- Meetings:
  - meeting:read:admin / meeting:read:master (View meetings)
  - meeting:write:admin / meeting:write:master (Create and update meetings)
  - meeting:delete:admin / meeting:delete:master (Delete meetings)
- Users: user:read:admin
- Recordings: recording:read:admin
Get your Client ID, Client Secret, and Account ID from the "App Credentials" tab.
Set them as environment variables in your Clawdbot config:
- ZOOM_CLIENT_ID
- ZOOM_CLIENT_SECRET
- ZOOM_ACCOUNT_ID

Commands

List Meetings

node {baseDir}/scripts/zoom-cli.js list

Create a Meeting

node {baseDir}/scripts/zoom-cli.js create "Meeting Topic" "2026-01-30T10:00:00Z" 60

Update a Meeting

node {baseDir}/scripts/zoom-cli.js update <meeting_id> <new_start_time> <duration> "New Topic"

Get Meeting Info

node {baseDir}/scripts/zoom-cli.js info <meeting_id>

Delete a Meeting

node {baseDir}/scripts/zoom-cli.js delete <meeting_id>

Source

git clone https://clawhub.ai/vnagin/zoom-manager-clawdView on GitHub

Overview

Zoom Manager lets you control Zoom meetings directly from Clawdbot without a browser. It supports the full meeting lifecycle—create, list, update, and delete—via the Zoom REST API v2 using Server-to-Server OAuth, with default cloud recording for every session.

How This Skill Works

The skill uses a clean Node.js implementation to call Zoom REST API v2 endpoints. It authenticates with a Server-to-Server OAuth app and operates headlessly, driven by CLI commands or natural language inputs, with environment variables for client credentials and account ID.

When to Use It

Automate the full lifecycle of Zoom meetings (create, list, update, delete) from Clawdbot without the Zoom dashboard.
Implement enterprise-grade automation using Server-to-Server OAuth for secure authentication.
Ensure cloud recordings are captured by default for all meetings.
Integrate Zoom meeting workflows with CRM, calendars, or other automation pipelines.
Develop custom automation flows (e.g., auto-scheduling after CRM updates) with a developer-friendly Node.js setup.

Quick Start

Step 1: Create a Server-to-Server OAuth app in Zoom and set environment variables: ZOOM_CLIENT_ID, ZOOM_CLIENT_SECRET, ZOOM_ACCOUNT_ID.
Step 2: Inspect basics with: node {baseDir}/scripts/zoom-cli.js list
Step 3: Create a meeting example: node {baseDir}/scripts/zoom-cli.js create "Meeting Topic" "2026-01-30T10:00:00Z" 60

Best Practices

Use a Server-to-Server OAuth app and assign the correct scopes (meeting read/write, user read, recording read).
Store client credentials and account ID as environment variables: ZOOM_CLIENT_ID, ZOOM_CLIENT_SECRET, ZOOM_ACCOUNT_ID.
Test changes in a non-production meeting setup before applying to live rooms.
Validate meeting times with ISO 8601 timestamps and verify time zones to avoid mismatches.
Enable and standardize cloud recording as a default for consistency across sessions.

Example Use Cases

Automatically create a client intro meeting when a CRM opportunity reaches the 'Proposal' stage.
List upcoming meetings for an account and mirror them to an external calendar system.
Update a meeting's start time and topic after a reschedule in the CRM using the update command.
Delete meetings canceled in the CRM to keep Zoom dashboards clean.
Enforce cloud recording on all meetings to ensure sessions are captured without manual setup.

Frequently Asked Questions

Add this skill to your agents