Generated banner for Zoom General
Generated logo for Zoom General

Zoom General

OpenAIOfficialCreated by ZoomDistributed by OpenAI

  • Skill
  • Tool integration
  • Automation and integrations
  • MIT
  • Medium risk

From the author

Use when comparing products.
— the description by Zoom

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Zoom General serves as a strategic starting point for developers and architects to navigate the Zoom ecosystem. It provides a structured workflow to classify integration requirements, identify the correct Zoom product surface (such as APIs, SDKs, or webhooks), and determine the necessary authentication model. By guiding users through a decision-making process, it ensures that developers select the right tool for their specific use case before routing to more specialized skills.

What it does

  • Classifies integration jobs based on desired outcomes like embedding meetings or automating resources.
  • Maps requirements to specific Zoom surfaces including REST APIs, WebSockets, and various SDKs.
  • Provides guidance on selecting the correct authentication and scope model for an integration.
  • Facilitates routing to specialized skills once the product context is established.
  • Offers comparative context for tasks that span multiple Zoom product boundaries.

When to use it

  • When you are in the early stages of planning a Zoom integration and need to choose the right app type.
  • When you need to compare different Zoom surfaces to determine which fits your technical requirements.
  • When a task involves multiple Zoom products and requires a high-level architectural approach.
  • When you need to confirm the correct authentication flow for a specific integration scenario.

Advantages

  • Prevents premature selection of tools by enforcing a structured classification process.
  • Clarifies the distinction between user-level OAuth, account-level OAuth, and SDK signatures.
  • Reduces complexity by routing users to narrow, specialized skills after initial planning.
  • Provides a clear decision matrix for choosing between General Apps, Server-to-Server OAuth, and Webhook Only apps.

Usage examples

“I want to build an app that automates meeting reports. Which Zoom app type should I use?”
The agent will guide you to classify the job as backend automation, leading to the recommendation of Server-to-Server OAuth for its lack of user interaction requirements.
“Should I use the Meeting SDK or the Video SDK for my project?”
The agent will help you compare the two based on your specific embedding needs and surface requirements, ensuring you choose the correct SDK for your use case.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/openai/zoom-general/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip zoom-general.zip -d .agents/skills

Documentation by Zoom

Zoom General

Use this skill for cross-product platform context after the user’s goal is understood. For first-step routing, prefer start, plan-zoom-product, or plan-zoom-integration.

Workflow

  1. Classify the job by outcome: embed meetings, custom video, automate resources, consume events, process media, use meeting intelligence, or publish a Marketplace app.

  2. Choose the Zoom surface that owns the behavior: REST API, webhooks, WebSockets, Meeting SDK, Video SDK, Zoom Apps SDK, Phone, Contact Center, Virtual Agent, Scribe, Rivet, or Cobrowse.

  3. Confirm auth and scope model before implementation; Zoom surfaces differ on user-level OAuth, account-level OAuth, and SDK signatures.

  4. Route to the narrow skill once the surface is chosen rather than keeping broad guidance in context.

  5. Use the preserved guide only when a task crosses product boundaries or needs detailed comparison tables.

References

Files

use-cases/testing-development.md

Testing & Development Environment

Set up development and testing environments for Zoom integrations.

Overview

Zoom provides several options for development and testing:

  • Development app credentials (separate from production)

  • Test accounts

  • Local webhook testing tools

  • SDK sandbox modes

Skills Needed

  • general - App configuration

  • webhooks - Webhook testing


Development vs Production Apps

Create Separate Apps

Always create separate apps for development and production:

EnvironmentPurposeCredentials
DevelopmentTesting, debuggingDev Client ID/Secret
ProductionLive usersProd Client ID/Secret
  1. Go to Zoom Marketplace

  2. Create "MyApp - Development" for testing

  3. Create "MyApp - Production" for live deployment

  4. Use environment variables to switch between them

// .env.development
ZOOM_CLIENT_ID=dev_client_id_here
ZOOM_CLIENT_SECRET=dev_secret_here
ZOOM_ACCOUNT_ID=dev_account_id

// .env.production
ZOOM_CLIENT_ID=prod_client_id_here
ZOOM_CLIENT_SECRET=prod_secret_here
ZOOM_ACCOUNT_ID=prod_account_id

Test Accounts

Option 1: Developer Account

Use your own Zoom account for initial development:

  • Free tier works for basic API testing

  • Pro account needed for SDK testing

  • Create test meetings manually

Option 2: Zoom Developer Sandbox (ISV Partners)

ISV partners can request sandbox accounts:

  • Contact Zoom partnership team

  • Isolated test environment

  • Multiple test users

Option 3: Programmatic Test Users

Create test users via API (requires admin account):

// Create a test user
const response = await axios.post(
  'https://api.zoom.us/v2/users',
  {
    action: 'create',
    user_info: {
      email: '[email protected]',  // Use + alias
      type: 1,  // Basic user
      first_name: 'Test',
      last_name: 'User'
    }
  },
  { headers: { 'Authorization': `Bearer ${accessToken}` }}
);

Tip: Use email aliases ([email protected], [email protected]) that all route to one inbox.


Local Webhook Testing

Expose your local development webhook server to the internet for testing:

# Install ngrok
npm install -g ngrok

# Start your local server
node server.js  # Running on port 3000

# In another terminal, create tunnel
ngrok http 3000

Output:

Forwarding  https://abc123.ngrok.io -> http://YOUR_DEV_HOST:3000

Use https://abc123.ngrok.io/webhook as your webhook URL in Zoom Marketplace.

Option 2: Cloudflare Tunnel
# Install cloudflared
brew install cloudflare/cloudflare/cloudflared

# Create tunnel
LOCAL_WEBHOOK_BASE_URL="http://YOUR_DEV_HOST:3000"
cloudflared tunnel --url "$LOCAL_WEBHOOK_BASE_URL"
Option 3: localtunnel
npm install -g localtunnel
lt --port 3000
Webhook URL Validation

Zoom requires validating your webhook endpoint. Your server must respond to the challenge:

app.post('/webhook', (req, res) => {
  // Handle Zoom's endpoint validation
  if (req.body.event === 'endpoint.url_validation') {
    const hashForValidate = crypto
      .createHmac('sha256', ZOOM_WEBHOOK_SECRET)
      .update(req.body.payload.plainToken)
      .digest('hex');

    return res.json({
      plainToken: req.body.payload.plainToken,
      encryptedToken: hashForValidate
    });
  }

  // Handle actual events
  // ...
});

SDK Development Mode

Meeting SDK Web

Enable debug logging:

const client = ZoomMtgEmbedded.createClient();

client.init({
  debug: true,  // Enable debug logs
  zoomAppRoot: document.getElementById('meetingSDKElement'),
  language: 'en-US',
});
Video SDK Web
const client = ZoomVideo.createClient();

await client.init('en-US', 'CDN', {
  enforceMultipleVideos: true,
  stayAwake: true,
  patchJsMedia: true,
  leaveOnPageUnload: true,
});

// Enable debug mode
ZoomVideo.setLogLevel('debug');
Native SDKs (iOS/Android/Desktop)

Enable verbose logging:

// iOS
let initParams = ZoomVideoSDKInitParams()
initParams.enableLog = true
initParams.logFilePrefix = "videosdk_debug"
// Android
val initParams = ZoomVideoSDKInitParams().apply {
    enableLog = true
    logFilePrefix = "videosdk_debug"
}

Mock Webhook Events

Manual Testing with curl

Test your webhook handler locally:

LOCAL_WEBHOOK_BASE_URL="http://YOUR_DEV_HOST:3000"

# Simulate meeting.started event
curl -X POST "$LOCAL_WEBHOOK_BASE_URL/webhook" \
  -H "Content-Type: application/json" \
  -H "x-zm-signature: v0=test" \
  -H "x-zm-request-timestamp: $(date +%s)" \
  -d '{
    "event": "meeting.started",
    "payload": {
      "account_id": "abc123",
      "object": {
        "id": "123456789",
        "uuid": "abcd-1234-efgh",
        "topic": "Test Meeting",
        "host_id": "xyz789"
      }
    }
  }'
Webhook Replay Tool

Build a simple replay tool for testing:

const fs = require('fs');

// Save incoming webhooks to file
app.post('/webhook', (req, res) => {
  const filename = `webhooks/${Date.now()}_${req.body.event}.json`;
  fs.writeFileSync(filename, JSON.stringify(req.body, null, 2));

  // Process normally...
});

// Replay saved webhook
async function replayWebhook(filename) {
  const payload = JSON.parse(fs.readFileSync(filename));
  await processWebhook(payload);
}

Testing Checklist

Before Going Live
  • [ ] Test OAuth flow end-to-end

  • [ ] Verify webhook signature validation

  • [ ] Test with multiple user types (host, participant, admin)

  • [ ] Handle rate limiting gracefully

  • [ ] Test error scenarios (invalid tokens, network failures)

  • [ ] Verify recording download permissions

  • [ ] Test SDK on all target platforms

  • [ ] Load test with expected user volume

API Testing
// Test helper for API calls
async function testAPICall(name, fn) {
  console.log(`Testing: ${name}`);
  try {
    const result = await fn();
    console.log(`Pass: ${name}`);
    return result;
  } catch (error) {
    console.error(`Fail: ${name}:`, error.message);
    throw error;
  }
}

// Run tests
await testAPICall('Create meeting', () =>
  createMeeting({ topic: 'Test' })
);
await testAPICall('Get meeting', () =>
  getMeeting(meetingId)
);
await testAPICall('Delete meeting', () =>
  deleteMeeting(meetingId)
);

Debugging Tips

Enable Request Logging
const axios = require('axios');

// Log all requests
axios.interceptors.request.use(config => {
  console.log(`-> ${config.method.toUpperCase()} ${config.url}`);
  return config;
});

axios.interceptors.response.use(
  response => {
    console.log(`<- ${response.status} ${response.config.url}`);
    return response;
  },
  error => {
    console.error(`<- ${error.response?.status} ${error.config?.url}`);
    console.error('Error:', error.response?.data);
    throw error;
  }
);
SDK Log Collection

See SDK Logs & Troubleshooting for collecting SDK debug logs.

Resources

Requirements and compatibility

Written for: OpenAI Codex

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

What our scanner noticed· Medium risk

  • Possible data-exfiltration endpoints
  • Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by
Zoom
Publisher
OpenAI (Official)
Distributed by
OpenAI
Source
openai/plugins · plugins/zoom/skills/general · commit d420d13
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from plugins/zoom/LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Zoom or OpenAI.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download zoom-general.zip