Zoom Apps SDK
OpenAIOfficialCreated by ZoomDistributed by OpenAI
- Skill
- Tool integration
- Software development
- MIT
- Medium risk
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The Zoom Apps SDK skill provides a structured approach for developers building applications that run directly inside the Zoom client. It covers the lifecycle of a Zoom App, from initial configuration and context verification to implementing advanced features like the Layers API, in-client OAuth, and inter-instance communication. The skill emphasizes the importance of identifying the correct running context—such as meetings, webinars, or the main client—to ensure features are gated appropriately and the user experience remains consistent across different Zoom environments.
What it does
- Initializes the Zoom Apps SDK with required capabilities.
- Identifies the current running context, such as meeting or main client.
- Facilitates in-client OAuth flows for secure user authentication.
- Enables communication between different app instances.
- Provides access to meeting-specific data and participant information.
- Supports advanced UI and media features like virtual backgrounds and notification management.
When to use it
- When building an application intended to run inside the Zoom client interface.
- When you need to access meeting context, participant lists, or recording status.
- When implementing custom UI overlays or media controls within a Zoom meeting.
- When you need to authenticate users without redirecting them to an external browser.
Advantages
- Provides a unified API for interacting with various Zoom client contexts.
- Supports secure, in-client authentication workflows.
- Enables deep integration with Zoom meeting features and participant data.
- Offers clear patterns for handling cross-instance communication.
Usage examples
- “How do I initialize the Zoom Apps SDK?”
- You must call zoomSdk.config() first, passing in the required capabilities and version to initialize the SDK and declare the features your app intends to use.
- “How can I get the current meeting ID?”
- After initializing the SDK, you can call zoomSdk.getMeetingContext() to retrieve the meetingID, meetingTopic, and meetingStatus.
- “How do I trigger authentication within the Zoom client?”
- Use the zoomSdk.authorize() method to trigger the in-client OAuth flow, which avoids external browser redirects and fires an onAuthorized event upon completion.
- “How do I send a message to another instance of my app?”
- First call zoomSdk.connect() to establish the connection, then use zoomSdk.postMessage() to send a payload to other app instances.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/openai/zoom-apps-sdk/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip zoom-apps-sdk.zip -d .agents/skills
Documentation by Zoom
Zoom Apps SDK
Use this skill when the app runs inside the Zoom client. If the user only needs to embed a meeting in an external app, route to Meeting SDK instead.
Workflow
Confirm the running context: meeting, webinar, main client, phone, collaborate mode, immersive mode, camera mode, or Layers API.
Configure Marketplace app settings, allowed domains, redirect URIs, and in-client OAuth before implementing SDK calls.
Initialize
zoomSdkand gate features by capability and running context.Design client communication and data flow: frontend SDK calls, backend REST calls, in-client OAuth tokens, and webhook handoff.
Implement advanced client features only after the base app loads reliably: Layers API, breakout rooms, guest mode, collaborate mode, or ZMail.
Debug blank panels, domain allowlist issues, CSP, missing capabilities, running-context mismatch, and OAuth redirect problems independently.
References
Full preserved guide: references/full-guide.md
Architecture: concepts/architecture.md
Running contexts: concepts/running-contexts.md
Meeting SDK versus Zoom Apps: concepts/meeting-sdk-vs-zoom-apps.md
Layers API: references/layers-api.md
In-client OAuth: examples/in-client-oauth.md
Common issues: troubleshooting/common-issues.md
Files
- ATTRIBUTION.mdAdded by AutoGineer873 B
- LICENSELicence file added by AutoGineer1.1 KiB
- RUNBOOK.md3.3 KiB
- SKILL.md1.5 KiB
- agents/openai.yaml130 B
- concepts/architecture.md7.7 KiB
- concepts/meeting-sdk-vs-zoom-apps.md1.0 KiB
- concepts/running-contexts.md5.6 KiB
- concepts/security.md5.4 KiB
- examples/app-communication.md3.6 KiB
- examples/breakout-rooms.md3.2 KiB
- examples/collaborate-mode.md4.1 KiB
- examples/guest-mode.md3.5 KiB
- examples/in-client-oauth.md6.1 KiB
- examples/layers-camera.md5.7 KiB
- examples/layers-immersive.md7.9 KiB
- examples/quick-start.md7.3 KiB
- references/apis.md5.3 KiB
- references/environment-variables.md1.1 KiB
- references/events.md3.8 KiB
- references/full-guide.md24.9 KiB
- references/layers-api.md15.8 KiB
- references/oauth.md5.3 KiB
- references/zmail-sdk.md5.5 KiB
- troubleshooting/common-issues.md4.3 KiB
- troubleshooting/debugging.md3.5 KiB
- troubleshooting/forum-top-questions.md1.1 KiB
- troubleshooting/migration.md3.0 KiB
troubleshooting/debugging.md
Debugging Guide
Local development setup, ngrok configuration, and browser preview.
ngrok Setup
ngrok provides an HTTPS tunnel to your local server. Required because Zoom Apps need HTTPS.
# Install ngrok (https://ngrok.com)
# Then start tunnel:
ngrok http 3000Copy the https://xxxxx.ngrok.io URL.
ngrok Free Tier Limitation
Free ngrok URLs change every restart. You must update 4 places in Marketplace each time:
Home URL:
https://xxxxx.ngrok.ioRedirect URL:
https://xxxxx.ngrok.io/authOAuth Allow List:
https://xxxxx.ngrok.ioDomain Allow List:
xxxxx.ngrok.io(no protocol)
Tip: Get ngrok paid plan ($8/mo) for a stable subdomain (e.g., https://myapp.ngrok.io).
Marketplace Configuration for Local Dev
In Zoom Marketplace -> Your App:
Feature tab -> Zoom App
Home URL:
https://xxxxx.ngrok.ioShare URL (optional):
https://xxxxx.ngrok.io
Feature tab -> OAuth Redirect URL
Redirect URL for OAuth:
https://xxxxx.ngrok.io/authAdd Allow List:
https://xxxxx.ngrok.io
Feature tab -> Domain Allow List
xxxxx.ngrok.ioappssdk.zoom.us(if using CDN)
Scopes tab
zoomapp:inmeeting(minimum required)
Browser Preview Mode
Test your UI outside Zoom by implementing a fallback:
import zoomSdk from '@zoom/appssdk';
let isInZoom = false;
async function init() {
try {
const config = await zoomSdk.config({
capabilities: ['getMeetingContext', 'getUserContext'],
version: '0.16'
});
isInZoom = true;
initZoomApp(config);
} catch (error) {
isInZoom = false;
initBrowserPreview();
}
}
function initBrowserPreview() {
// Show mock UI with sample data for development
const mockMeeting = { meetingID: '123456789', meetingTopic: 'Test Meeting' };
const mockUser = { screenName: 'Dev User', role: 'host' };
renderApp(mockMeeting, mockUser);
console.log('Running in browser preview mode');
}Opening DevTools in Zoom
The Zoom client's embedded browser supports DevTools:
Windows
Open Zoom client
Open your Zoom App
Right-click inside the app panel
Select "Inspect Element" (if available)
Alternative: Remote Debugging
Start Zoom with remote debugging flag
Open
chrome://inspectin ChromeFind your app's WebView
Note: DevTools availability depends on Zoom client version and settings. Not all surfaces support it.
Environment Variables
Use .env file with dotenv:
# .env (never commit this file)
ZOOM_APP_CLIENT_ID=abc123
ZOOM_APP_CLIENT_SECRET=xyz789
ZOOM_APP_REDIRECT_URI=https://xxxxx.ngrok.io/auth
SESSION_SECRET=random-secret-string-here
ZOOM_HOST=https://zoom.us// server.js
require('dotenv').config();
// process.env.ZOOM_APP_CLIENT_ID is now availableAdd .env to .gitignore:
.env
.env.localCommon Dev Workflow
# Terminal 1: Start server
npm run dev
# Terminal 2: Start ngrok
ngrok http 3000
# Then:
# 1. Copy ngrok URL
# 2. Update Marketplace URLs (if changed)
# 3. Open Zoom client
# 4. Click your app in sidebar or during meeting
# 5. Check the ngrok local request inspector for request logsngrok Request Inspector
ngrok provides a local web UI that shows:
All HTTP requests to your tunnel
Request/response headers and bodies
Replay failed requests
This is invaluable for debugging OAuth redirects and API calls.
Resources
Testing guide: https://developers.zoom.us/docs/zoom-apps/guides/testing/
ngrok docs: https://ngrok.com/docs
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
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/zoom-apps-sdk · 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-apps-sdk.zip