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/saas-app-oauth-integration.md

Building a SaaS App with Zoom OAuth Integration

Create a multi-tenant SaaS application that integrates with Zoom using User OAuth for per-user authorization.

Scenario

You're building a meeting scheduling SaaS that needs to:

  • Allow users to authorize your app to access their Zoom account

  • Create meetings on behalf of users

  • List user's meetings

  • Store and refresh tokens securely per user

  • Handle token expiration and refresh automatically

Required Skills

  1. oauth - User authorization flow, token management

  2. zoom-rest-api - Meeting creation and management endpoints

Architecture

User Browser → Your SaaS App → Zoom OAuth → Zoom APIs
                 ↓
           Database (user tokens)

Implementation Steps

1. OAuth Setup (oauth)

Configure app in Zoom Marketplace:

  • App Type: OAuth

  • Redirect URL: https://yourapp.com/oauth/callback

  • Required scopes: meeting:write, meeting:read, user:read

See: oauth/concepts/oauth-flows.md#user-authorization-oauth

2. User Authorization Flow (oauth)
// Redirect user to Zoom authorization
app.get('/connect-zoom', (req, res) => {
  const state = generateSecureState();
  req.session.oauthState = state;

  res.redirect(
    `https://zoom.us/oauth/authorize?` +
    `response_type=code&` +
    `client_id=${CLIENT_ID}&` +
    `redirect_uri=${REDIRECT_URI}&` +
    `state=${state}`
  );
});

See: oauth/examples/user-oauth-mysql.md

3. Token Storage (oauth)

Store user tokens with encryption:

// After OAuth callback
const { access_token, refresh_token } = await exchangeCode(code);

await db.users.update({
  zoom_access_token: encrypt(access_token),
  zoom_refresh_token: encrypt(refresh_token),
  token_expiry: Date.now() + 3600000
}, { where: { id: userId } });

See: oauth/concepts/token-lifecycle.md#user-oauth--device-flow-token-lifecycle

4. Auto-Refresh Middleware (oauth)
// Automatically refresh expired tokens
const zoomTokenMiddleware = async (req, res, next) => {
  const user = await db.users.findByPk(req.session.userId);

  if (isTokenExpired(user.token_expiry)) {
    const newTokens = await refreshToken(user.zoom_refresh_token);
    await updateUserTokens(user.id, newTokens);
    req.zoomToken = newTokens.access_token;
  } else {
    req.zoomToken = decrypt(user.zoom_access_token);
  }

  next();
};

See: oauth/examples/token-refresh.md

5. Create Meetings (zoom-rest-api)
app.post('/api/meetings', zoomTokenMiddleware, async (req, res) => {
  const meeting = await axios.post(
    'https://api.zoom.us/v2/users/me/meetings',
    {
      topic: req.body.topic,
      type: 2, // Scheduled meeting
      start_time: req.body.start_time,
      duration: req.body.duration
    },
    {
      headers: { Authorization: `Bearer ${req.zoomToken}` }
    }
  );

  res.json(meeting.data);
});

See: zoom-rest-api skill for endpoint documentation

Security Considerations

Token Encryption (oauth)

MUST encrypt tokens at rest:

const crypto = require('crypto');

function encrypt(text) {
  const cipher = crypto.createCipher('aes-256-cbc', process.env.CIPHER_KEY);
  return cipher.update(text, 'utf8', 'hex') + cipher.final('hex');
}

See: oauth/examples/user-oauth-mysql.md#token-encryption

State Parameter (oauth)

Prevent CSRF attacks:

const state = crypto.randomBytes(16).toString('hex');
req.session.oauthState = state; // Verify in callback

See: oauth/concepts/state-parameter.md

Handling Edge Cases

User Revokes Access (webhooks)

Listen for deauthorization webhook:

app.post('/webhooks/zoom', (req, res) => {
  if (req.body.event === 'app_deauthorized') {
    const userId = req.body.payload.user_id;
    await deleteUserZoomTokens(userId);
  }
});

Chain to: webhooks skill for webhook setup

Refresh Token Expired (oauth)
try {
  await refreshToken(user.zoom_refresh_token);
} catch (error) {
  if (error.code === 4735) {
    // Refresh token expired - prompt re-authorization
    res.redirect('/connect-zoom');
  }
}

See: oauth/troubleshooting/token-issues.md

Testing Checklist

  • [ ] User authorization flow works

  • [ ] Tokens stored encrypted in database

  • [ ] Tokens auto-refresh before expiration

  • [ ] Meetings created successfully via API

  • [ ] Deauthorization webhook handled

  • [ ] Refresh token expiration handled

  • meeting-automation.md - Advanced meeting scheduling

  • user-and-meeting-creation.md - Bulk user/meeting operations

  • recording-download-pipeline.md - Download recordings via API

Skills Used

  • oauth (primary) - User OAuth, token management, PKCE

  • zoom-rest-api - Meeting and user API endpoints

  • webhooks - Deauthorization notifications

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