OpenParable
Skip to content
← Back to skills

Zoom Oauth

Apps & Automation
zoom-oauth

Zoom Oauth is an Agent Skill for apps & automation published in the openai/plugins repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Use when implementing OAuth.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/openai/plugins/blob/HEAD/plugins/zoom/skills/oauth/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/zoom-oauth, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Zoom OAuth

Use this skill for concrete Zoom authentication implementation and troubleshooting. Prefer setup-zoom-oauth for the first-pass setup plan, then return here for exact flows, scope behavior, refresh handling, and error diagnosis.

Workflow

  1. Identify the app type and actor: user-level OAuth, account-level OAuth, server-to-server OAuth where officially supported, SDK JWT, or Build-platform credentials.
  2. Confirm the target API, SDK, or app surface, because scopes and token audiences differ by surface.
  3. Choose the grant flow: authorization code with PKCE for public clients, authorization code for confidential web apps, device authorization where appropriate, or account credentials for supported account-level automation.
  4. Store refresh tokens as single-use values: persist the replacement refresh token returned by each refresh response before reusing the old one.
  5. Validate requests against redirect URI, account ID, scopes, app publication state, and token expiration before changing application code.
  6. For local development, keep access tokens out of logs and treat refresh tokens as single-use when rotating credentials.

References