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://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/user-and-meeting-creation.md

User and Meeting Creation Chain

Create a user account and immediately schedule a meeting for that user.

Overview

A common provisioning pattern: create a new Zoom user via REST API, wait for activation, then create a meeting for that user. This requires understanding user states and proper sequencing.

Skills Needed

OrderSkillPurpose
1zoom-rest-apiCreate user account
2zoom-rest-apiCreate meeting for user
(Optional)webhooksReceive user activation event

Skill Chaining Flow

┌─────────────────────────────────────────────────────────────────────────┐
│                        USER + MEETING CREATION FLOW                      │
└─────────────────────────────────────────────────────────────────────────┘

┌─────────────────────────────────────────────────────────────────────────┐
│ 1. Create User (zoom-rest-api)                                          │
│    └── POST /users                                                      │
│    └── action: "create" | "autoCreate" | "custCreate" | "ssoCreate"     │
│    └── Returns: user_id, status                                         │
└─────────────────────────────────────────────────────────────────────────┘
                                    │
                                    ▼
┌─────────────────────────────────────────────────────────────────────────┐
│ 2. Wait for User Activation                                             │
│    └── Option A: Poll GET /users/{userId} until status = "active"       │
│    └── Option B: Listen for user.activated webhook                      │
│    └── Option C: Use autoCreate (auto-activates)                        │
└─────────────────────────────────────────────────────────────────────────┘
                                    │
                                    ▼
┌─────────────────────────────────────────────────────────────────────────┐
│ 3. Create Meeting (zoom-rest-api)                                       │
│    └── POST /users/{userId}/meetings                                    │
│    └── Returns: meeting_id, join_url, start_url                         │
└─────────────────────────────────────────────────────────────────────────┘

Prerequisites

  • Zoom app with Server-to-Server OAuth (recommended) or OAuth

  • Scopes: user:write:admin, meeting:write:admin

  • Admin privileges on the Zoom account

  • See Authorization Patterns for RBAC and permission validation middleware

User Action Types

ActionDescriptionActivationBest For
createSends activation email to userUser clicks email linkStandard provisioning
autoCreateCreates pre-activated userImmediateAutomated systems
custCreateCreates user without emailManual activationCustom workflows
ssoCreateCreates SSO userSSO loginEnterprise SSO

Step 1: Create User

Option A: Standard Creation (with email activation)
const axios = require('axios');

/**
 * Create a new Zoom user
 * @param {Object} userInfo - User information
 * @param {string} accessToken - Valid OAuth access token
 * @returns {Promise<Object>} Created user details
 */
async function createUser(userInfo, accessToken) {
  try {
    const response = await axios.post(
      'https://api.zoom.us/v2/users',
      {
        action: 'create',  // Sends activation email
        user_info: {
          email: userInfo.email,
          type: userInfo.type || 1,  // 1=Basic, 2=Licensed
          first_name: userInfo.firstName,
          last_name: userInfo.lastName,
          password: userInfo.password  // Optional
        }
      },
      {
        headers: {
          'Authorization': `Bearer ${accessToken}`,
          'Content-Type': 'application/json'
        }
      }
    );

    return {
      id: response.data.id,
      email: response.data.email,
      first_name: response.data.first_name,
      last_name: response.data.last_name,
      type: response.data.type,
      status: 'pending'  // User needs to activate via email
    };
  } catch (error) {
    if (error.response?.status === 409) {
      throw new Error(`User ${userInfo.email} already exists`);
    }
    if (error.response?.status === 400) {
      throw new Error(`Invalid user data: ${error.response.data.message}`);
    }
    throw error;
  }
}
Option B: Auto-Create (Immediate activation)
/**
 * Create a pre-activated Zoom user (no email required)
 * Recommended for automated provisioning
 */
async function createUserAutoActivate(userInfo, accessToken) {
  try {
    const response = await axios.post(
      'https://api.zoom.us/v2/users',
      {
        action: 'autoCreate',  // User is immediately active
        user_info: {
          email: userInfo.email,
          type: userInfo.type || 2,  // 2=Licensed (required for autoCreate)
          first_name: userInfo.firstName,
          last_name: userInfo.lastName,
          password: userInfo.password || generateSecurePassword()
        }
      },
      {
        headers: {
          'Authorization': `Bearer ${accessToken}`,
          'Content-Type': 'application/json'
        }
      }
    );

    return {
      id: response.data.id,
      email: response.data.email,
      first_name: response.data.first_name,
      last_name: response.data.last_name,
      type: response.data.type,
      status: 'active'  // Ready immediately
    };
  } catch (error) {
    handleUserCreationError(error, userInfo.email);
  }
}

function generateSecurePassword() {
  const crypto = require('crypto');
  return crypto.randomBytes(16).toString('base64') + '!Aa1';
}

Step 2: Wait for User Activation

Option A: Polling (Simple)
/**
 * Wait for user to become active by polling
 * @param {string} userId - User ID to check
 * @param {string} accessToken - OAuth token
 * @param {number} maxWaitMs - Maximum wait time (default 5 minutes)
 * @param {number} pollIntervalMs - Poll interval (default 5 seconds)
 */
async function waitForUserActivation(userId, accessToken, maxWaitMs = 300000, pollIntervalMs = 5000) {
  const startTime = Date.now();

  while (Date.now() - startTime < maxWaitMs) {
    const user = await getUser(userId, accessToken);

    if (user.status === 'active') {
      console.log(`User ${userId} is now active`);
      return user;
    }

    console.log(`User ${userId} status: ${user.status}, waiting...`);
    await new Promise(resolve => setTimeout(resolve, pollIntervalMs));
  }

  throw new Error(`User ${userId} did not activate within ${maxWaitMs}ms`);
}

async function getUser(userId, accessToken) {
  const response = await axios.get(
    `https://api.zoom.us/v2/users/${userId}`,
    {
      headers: { 'Authorization': `Bearer ${accessToken}` }
    }
  );
  return response.data;
}
const express = require('express');
const app = express();
app.use(express.json());

// Store pending user creations
const pendingUsers = new Map();

/**
 * Create user and wait for webhook activation
 */
async function createUserAndWait(userInfo, accessToken) {
  // Create user
  const user = await createUser(userInfo, accessToken);

  // Set up promise that resolves when webhook fires
  return new Promise((resolve, reject) => {
    const timeout = setTimeout(() => {
      pendingUsers.delete(user.id);
      reject(new Error(`User ${user.id} activation timeout`));
    }, 300000); // 5 minute timeout

    pendingUsers.set(user.id, { resolve, reject, timeout, user });
  });
}

// Webhook handler for user activation
app.post('/webhooks/zoom', (req, res) => {
  const { event, payload } = req.body;

  if (event === 'user.activated') {
    const userId = payload.object.id;
    const pending = pendingUsers.get(userId);

    if (pending) {
      clearTimeout(pending.timeout);
      pendingUsers.delete(userId);
      pending.resolve({ ...pending.user, status: 'active' });
    }
  }

  res.status(200).send();
});

Step 3: Create Meeting for User

/**
 * Create a meeting for a specific user
 * @param {string} userId - User ID or email
 * @param {Object} meetingInfo - Meeting details
 * @param {string} accessToken - OAuth token
 */
async function createMeetingForUser(userId, meetingInfo, accessToken) {
  try {
    const response = await axios.post(
      `https://api.zoom.us/v2/users/${userId}/meetings`,
      {
        topic: meetingInfo.topic,
        type: meetingInfo.type || 2,  // 2 = Scheduled
        start_time: meetingInfo.startTime,
        duration: meetingInfo.duration || 60,
        timezone: meetingInfo.timezone || 'UTC',
        agenda: meetingInfo.agenda,
        settings: {
          host_video: true,
          participant_video: true,
          join_before_host: false,
          mute_upon_entry: true,
          waiting_room: true,
          ...meetingInfo.settings
        }
      },
      {
        headers: {
          'Authorization': `Bearer ${accessToken}`,
          'Content-Type': 'application/json'
        }
      }
    );

    return {
      id: response.data.id,
      topic: response.data.topic,
      start_time: response.data.start_time,
      join_url: response.data.join_url,
      start_url: response.data.start_url,
      password: response.data.password,
      host_id: response.data.host_id,
      host_email: response.data.host_email
    };
  } catch (error) {
    if (error.response?.status === 404) {
      throw new Error(`User ${userId} not found or not active`);
    }
    if (error.response?.status === 429) {
      throw new Error('Rate limit exceeded. Try again later.');
    }
    throw error;
  }
}

Complete Chained Operation

/**
 * Complete example: Create user and schedule their first meeting
 *
 * This demonstrates skill chaining:
 * 1. zoom-rest-api (users) - Create user
 * 2. zoom-rest-api (meetings) - Create meeting
 */

async function provisionUserWithMeeting(userInfo, meetingInfo) {
  console.log('Starting user provisioning...');

  // Get access token
  const accessToken = await getAccessToken();

  try {
    // Step 1: Create user (autoCreate for immediate activation)
    console.log(`Creating user: ${userInfo.email}`);
    const user = await createUserAutoActivate({
      email: userInfo.email,
      firstName: userInfo.firstName,
      lastName: userInfo.lastName,
      type: 2  // Licensed user
    }, accessToken);

    console.log(`User created: ${user.id} (status: ${user.status})`);

    // Step 2: Verify user is active (should be immediate with autoCreate)
    if (user.status !== 'active') {
      console.log('Waiting for user activation...');
      await waitForUserActivation(user.id, accessToken);
    }

    // Step 3: Create meeting for the new user
    console.log(`Creating meeting for user: ${user.id}`);
    const meeting = await createMeetingForUser(user.id, {
      topic: meetingInfo.topic || `${user.first_name}'s Meeting`,
      type: 2,
      startTime: meetingInfo.startTime || new Date(Date.now() + 3600000).toISOString(),
      duration: meetingInfo.duration || 60,
      timezone: meetingInfo.timezone || 'America/Los_Angeles'
    }, accessToken);

    console.log(`Meeting created: ${meeting.id}`);

    // Return complete provisioning result
    return {
      success: true,
      user: {
        id: user.id,
        email: user.email,
        name: `${user.first_name} ${user.last_name}`
      },
      meeting: {
        id: meeting.id,
        topic: meeting.topic,
        join_url: meeting.join_url,
        start_url: meeting.start_url,
        start_time: meeting.start_time
      }
    };

  } catch (error) {
    console.error('Provisioning failed:', error.message);

    // Cleanup: If user was created but meeting failed, optionally delete user
    // await deleteUser(user.id, accessToken);

    return {
      success: false,
      error: error.message
    };
  }
}

// Helper: Get access token (Server-to-Server OAuth)
async function getAccessToken() {
  const credentials = Buffer.from(
    `${process.env.ZOOM_CLIENT_ID}:${process.env.ZOOM_CLIENT_SECRET}`
  ).toString('base64');

  const response = await axios.post(
    `https://zoom.us/oauth/token?grant_type=account_credentials&account_id=${process.env.ZOOM_ACCOUNT_ID}`,
    null,
    { headers: { 'Authorization': `Basic ${credentials}` } }
  );

  return response.data.access_token;
}

// Usage
const result = await provisionUserWithMeeting(
  {
    email: '[email protected]',
    firstName: 'John',
    lastName: 'Doe'
  },
  {
    topic: 'Onboarding Meeting',
    startTime: '2024-02-01T10:00:00Z',
    duration: 30
  }
);

console.log(result);
// {
//   success: true,
//   user: { id: 'abc123', email: '[email protected]', name: 'John Doe' },
//   meeting: { id: '123456789', topic: 'Onboarding Meeting', join_url: '...', ... }
// }

Error Handling

Error Recovery Pattern
/**
 * Robust provisioning with rollback capability
 */
async function provisionUserWithMeetingSafe(userInfo, meetingInfo) {
  const accessToken = await getAccessToken();
  let createdUser = null;

  try {
    // Step 1: Create user
    createdUser = await createUserAutoActivate(userInfo, accessToken);

    // Step 2: Create meeting
    const meeting = await createMeetingForUser(createdUser.id, meetingInfo, accessToken);

    return { success: true, user: createdUser, meeting };

  } catch (error) {
    // Rollback: Delete user if meeting creation failed
    if (createdUser && error.message.includes('meeting')) {
      console.log(`Rolling back: deleting user ${createdUser.id}`);
      try {
        await deleteUser(createdUser.id, accessToken);
      } catch (deleteError) {
        console.error('Rollback failed:', deleteError.message);
      }
    }

    throw error;
  }
}

async function deleteUser(userId, accessToken) {
  await axios.delete(
    `https://api.zoom.us/v2/users/${userId}?action=delete`,
    {
      headers: { 'Authorization': `Bearer ${accessToken}` }
    }
  );
}
Common Errors
ErrorCauseSolution
409 ConflictUser email already existsUse existing user or different email
400 Bad RequestInvalid user dataCheck email format, required fields
404 Not FoundUser not active/foundWait for activation or verify user ID
429 Rate LimitToo many requestsImplement backoff, batch operations
201 but pendingUser needs to activateUse autoCreate or wait for activation

User Types Reference

TypeValueDescriptionCan Host?
Basic1Free userLimited
Licensed2Paid licenseYes
On-prem3On-premise deploymentYes
None99No licenseNo

Best Practices

  1. Use autoCreate for automation - Avoids waiting for email activation

  2. Implement rollback logic - Clean up if later steps fail

  3. Cache access tokens - Tokens are valid for 1 hour

  4. Handle rate limits - Implement exponential backoff

  5. Validate input early - Check email format before API calls

  6. Log all operations - Aids debugging and audit

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