build-zoom-team-chat-app — Claude command for Zoom Team Chat
A Claude and Claude command that walks the agent through building a Zoom Team Chat integration or chatbot: auth, eventing, message handling.
~/.codex/prompts/build-zoom-team-chat-app.mdWhat build-zoom-team-chat-app does
Reach for this command when the repo has to send, receive or automate Zoom Team Chat messages, cards, commands or chatbot interactions. The agent starts by reading the codebase: existing chat app routes, OAuth handling, webhook handlers, message templates. Then it works out which flow you are building — user-scoped messaging, chatbot behaviour, slash-command handling or notifications — and which runtime will own incoming events and outgoing message calls.
Before touching files, the command asks for a plan: the Team Chat workflow, the files to change, the auth path, the inbound event path and the outbound message path, plus how the message flow gets verified. From there the agent adds or fixes auth, event handlers and outbound logic, keeps to the repo's existing route and event patterns, and adds just enough message formatting or card logic for a useful first pass. Secrets and user tokens stay out of output and logs, and chat event handling is kept apart from unrelated webhook logic where possible.
Verification means re-reading the changed handlers, auth code and formatting, running a local build or tests, and confirming the shape of the inbound and outbound path. If webhook delivery fails, the command points you at /debug-zoom-webhook. One thing to know up front: a missing app configuration, event subscription or scope gap will stop the work, and the command asks the agent to name that blocker instead of papering over it.
What it helps with
- send Zoom Team Chat messages from a backend service
- receive and parse inbound chat events
- wire up OAuth and event subscriptions for a chat app
- ship a first pass at cards and slash commands
- separate chat event handling from unrelated webhook logic
Example prompts for the agent
- Implement Zoom Team Chat notifications in this repo
- Add an inbound Team Chat event handler and verify the message path
- Figure out why webhooks are not arriving and fix the event subscription
How to install build-zoom-team-chat-app
Manually: put the files in place
~/.codex/prompts/build-zoom-team-chat-app.mdCall it with /prompts:build-zoom-team-chat-app. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.claude/commands/build-zoom-team-chat-app.mdCall it with /build-zoom-team-chat-app. For all projects use ~/.claude/commands/
Manually: put the files in place
.github/prompts/build-zoom-team-chat-app.prompt.mdManually: put the files in place
.gemini/commands/build-zoom-team-chat-app.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about build-zoom-team-chat-app
How do I install build-zoom-team-chat-app in Claude?
Place the command file at ~/.codex/prompts/build-zoom-team-chat-app.md. It is then available as a prompt in Claude.
What does build-zoom-team-chat-app do?
It guides the agent through a Zoom Team Chat integration or chatbot: codebase inspection, a plan, auth and event handler changes, outbound message logic and verification of the message path.
What does the command need to work?
A configured Zoom app, an event subscription and the right scopes. When something is missing, the command asks the agent to state it as a blocker. On webhook delivery failure it points to /debug-zoom-webhook.
Source text
build-zoom-team-chat-app.md · MIT
--- description: Implement a Zoom Team Chat integration or chatbot flow with the right auth, eventing, and message handling. --- # Build Zoom Team Chat App Use this command when the repo should send, receive, or automate Zoom Team Chat messages, cards, commands, or chatbot interactions. ## Preflight 1. Inspect the codebase for existing chat app routes, OAuth handling, webhook handlers, and message templates. 2. Identify whether the workflow is user-scoped messaging, chatbot behavior, slash-command handling, or notifications. 3. Confirm the runtime that will own incoming events and outgoing message calls. 4. Check for the required auth and event configuration without printing secrets. ## Plan Before making changes: - state the Team Chat workflow being implemented - list the files that will be changed - state the auth path, inbound event path, and outbound message path - state how the message flow will be verified ## Commands 1. Add or correct Team Chat auth, event handlers, and outbound message logic. 2. Keep the implementation aligned with the repo’s existing event and route patterns. 3. Add the minimum message formatting or card logic required for a useful first pass. 4. Keep secrets and user tokens out of output and logs. 5. Separate chat event handling from unrelated webhook logic where possible. ## Verification 1. Re-read the event handlers, auth code, and message formatting logic that changed. 2. Run local build or tests where available. 3. Verify the inbound and outbound message path shape. 4. State any remaining blocker such as missing app configuration, event subscription, or scope gap. ## Summary ```text ## Result - Action: implemented or updated a Zoom Team Chat workflow - Status: success | partial | failed - Details: files changed, auth path, event path, verification run ``` ## Next Steps - Send one real message flow through the app. - Add richer cards or commands only after the base message path works. - If webhook delivery fails, run `/debug-zoom-webhook`.
© Zoom · MIT · openai/plugins
