build-zoom-team-chat-app
Reference skill for Zoom Team Chat. Use after routing to a chat workflow when building user-scoped messaging integrations, chatbot experiences, rich cards, buttons, slash commands, or chat webhooks.
Security Assessment
About build-zoom-team-chat-app
Build Zoom Team Chat App is a large reference skill (38 files) for building Zoom Team Chat integrations, from user-scoped messaging to interactive chatbots with rich cards, buttons, dropdowns, slash commands, and webhooks. Its central problem is that Team Chat has two non-interchangeable integration types, and choosing the wrong one early causes cascading auth, scope, and endpoint mismatches. The skill makes that decision explicit up front and then guides the full build.
It clearly distinguishes the Team Chat API (user type, User OAuth authorization_code flow, `/v2/chat/users/...` endpoints, messages as a real user) from the Chatbot API (bot type, Client Credentials grant, `/v2/im/chat/messages`, messages as the bot with rich cards). Bundled material covers environment setup, credential and scope configuration, OAuth flows, sending messages, message-card components, webhook events and verification, rate limits, error codes, JID formats, database integration, LLM integration, and troubleshooting guides for OAuth, webhooks, messages, and deployment. Setup docs walk through creating a General App (explicitly not Server-to-Server OAuth), configuring redirect URLs, obtaining Client ID/Secret/Account ID/Bot JID, and populating a `.env` file, which is standard, security-conscious credential setup.
It targets developers building Zoom notifications, user-automation, or interactive chatbots. Use cases range from CI/CD notifications via the Team Chat API to fully interactive bots handling button clicks, form submissions, and slash commands. Prerequisites include a Zoom account with an appropriate developer role and a marketplace app. This is documentation and code-pattern guidance grounded in official Zoom docs.
FAQ
Why does the skill emphasize choosing an API type first?
Team Chat has two non-interchangeable types, the Team Chat API (user, User OAuth) and the Chatbot API (bot, Client Credentials). Picking the wrong one early makes auth, scopes, and endpoints mismatch and the build fails.
When should I use the Chatbot API vs the Team Chat API?
Use the Team Chat API to send notifications or automate messages as a user (for example from CI/CD). Use the Chatbot API for interactive bots with buttons, forms, dropdowns, and slash commands.
What are the prerequisites?
A Zoom account with account owner/admin or the 'Zoom for developers' role, and a marketplace General App (OAuth), explicitly not Server-to-Server OAuth, which lacks Team Chat/Chatbot features.
How are credentials handled?
You collect Client ID, Client Secret, Account ID, Bot JID, and a webhook Secret Token from the app dashboard and store them in a .env file, standard local credential configuration used to authenticate API calls and verify webhook signatures.
What does the reference material include?
OAuth setup, message sending, rich message cards, webhook events, rate limits, error codes, JID formats, LLM and database integration examples, and troubleshooting for OAuth, webhooks, messages, and deployment.
All Files
38 filesInstall build-zoom-team-chat-app
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
anthropics/knowledge-work-plugins