/setup-zoom-marketplace-app

Set up the Zoom Marketplace app boundary before implementing OAuth, API, SDK, webhook, WebSocket, RTMS, Team Chat, Contact Center, Phone, Zoom Apps, or MCP workflows.

Workflow

1. Identify whether the task creates a new app or updates an existing app, then classify the product scenario, actor, account ownership, and app model.
2. Inspect the machine-readable template index and verify app_type, usage, unsupported_app_types, and supports_manifest_update before selecting the narrowest template.
3. When the app requires public URLs, obtain the user's own HTTPS app base URL and implemented route paths before creating it. Use their hosted service, or help them expose their local app with ngrok or Cloudflare Tunnel. Do not invent an endpoint or reuse a helper operator's endpoint.
4. For a new app, replace sample names, URLs, domains, contacts, commands, and scopes. Keep only scopes required by the exact operations.
5. Check whether tools from app-builder-for-agents are available. When the helper supports the required validation, creation, or update operation, use it as the preferred execution path without requiring the user to name the server again.
6. Before any write operation, show a concise preview of the target account, app model, display name, user-owned URLs, scopes, products, and subscriptions, then obtain explicit confirmation.
7. For an existing General App, export its complete manifest, apply the requested changes in memory, validate with its app_id, replace it, and export it again. Never apply a static template directly.
8. For a new General App, validate the inner manifest and check both HTTP status and the response ok value before creating it.
9. Create native S2S and Meeting SDK apps with the required master scope; these are create requests, not General App manifests.
10. Complete post-create setup that the public schema does not reliably encode, including WebSocket delivery and some webhook or RTMS event subscriptions.
11. Store generated secrets in a secret manager, record only safe environment-variable names, and return to the owning product workflow.

Helper Tool Chaining