Zoom Team Chat configuration guide
1. Prerequisites
- You have Owner or Admin permissions for the Zoom account and can create and install apps
- You have admin permissions on the Agentic Engine platform
- Agentic Engine has a public HTTPS address that Zoom can access
- An existing Zoom Team Chat channel for testing group chat messages
2. Create a Zoom App and get credentials
Go to Zoom App Marketplace and follow these steps:
- Go to Develop → Build App and create a General App
- For internal use within your organization, select Admin-managed. During development and testing, you can use the Development environment first
- Enter the app name, description, and developer contact information
- In the app features, enable Zoom Team Chat / Chat Subscription
- Create a Slash Command. You can customize the command name, such as
/ae. Leave Bot Endpoint URL empty for now and fill it in after you finish the platform channel configuration in the next section - In Scopes, make sure the app includes the
imchat:botscope. If it doesn't, add it manually - Record the following information from the current app environment:
| Credential | Description |
|---|---|
| Client ID | Client identifier of the Zoom app |
| Client Secret | Client secret paired with the Client ID |
| Secret Token | Used to verify Zoom callback requests |
| Bot JID | Identity of the Chatbot, usually in the form robot_xxxxx@xmpp.zoom.us |
| Account ID | Identifier of the current Zoom account |
Client Secret and Secret Token are sensitive credentials. Don't commit them to a code repository or send them in chats or tickets. Development and Production credentials must be used as complete sets and can't be mixed.
3. Add a Zoom Team Chat channel on the platform
As an admin, log in to Agentic Engine and go to System Admin > Agent Management > Channels:
- Click New Channel and select Zoom Team Chat as the channel type
- Fill in the following configuration items:
| Config items | Required | Description |
|---|---|---|
| Channel Name | Required | Display name, such as "Zoom Team Chat" |
| Client ID | Required | Client ID of the Zoom app |
| Client Secret | Required | Client Secret of the Zoom app |
| Secret Token | Required | Secret Token of the Zoom app's Chat Subscription |
| Bot JID | Required | Bot JID of the Zoom Chatbot |
| Account ID | Required | Account ID of the account that owns the Zoom app |
| Bound model | Optional | If left empty, the system default model is used |
| System Prompt | Optional | Agent-specific System Prompt for this channel |
- Save the channel, return to the channel list, and click Verify credentials
- After verification succeeds, enable the channel
- Edit the channel again and copy the read-only Bot Endpoint URL
- Return to Zoom App Marketplace, paste the address into Bot Endpoint URL under Chat Subscription, complete Endpoint URL Validation, and then save
- Install the app to the current account or test scope as required on the Zoom page
Before Endpoint URL Validation, the Agentic Engine channel must have passed credential verification and be enabled. When you edit an existing channel, leaving Client Secret and Secret Token empty keeps their original values.
4. Users bind their Zoom accounts
Before using it for the first time, regular users need to bind their Zoom account to their Agentic Engine account:
- Go to Account > Channel Accounts and select the Zoom Team Chat channel you want to use
- Copy the one-time binding code generated by the system, such as
+bind ABC234 - Open Zoom Workplace → Team Chat, find the Chatbot installed by the admin, and open a direct message with the bot
- Send the binding code with the Slash Command that the admin actually configured. For example, if the command is
/ae, send/ae +bind ABC234 - After you receive the binding success message, you can start using it. To unbind, go back to the Channel Accounts page
The binding code is valid for 10 minutes and can be used successfully only once. The binding command works only in a direct message with the bot. Sending it in a channel doesn't complete the binding and doesn't use up the binding code.
A Zoom account can't be bound to multiple Agentic Engine users at the same time. If a message says the account is already bound to another user, unbind it from the original user first.
5. Group chat message routing
Group chat message routing lets the same Zoom Chatbot hand different questions to different Agents or Teams based on rules. Rules are configured on the entry that corresponds to the current Zoom app and Account ID, and they apply to Team Chat channels the Chatbot has joined. Users must have bound an Agentic Engine account and start tasks with the Slash Command configured by the admin. Regular channel messages or simply @mentioning the bot don't reach Agentic Engine.
Additional permission checks
The app must include the imchat:bot scope and be installed to the current Zoom account. To use it in a channel, a member with permission must also add the app to that Team Chat channel.
Admin setup
- Add the Chatbot to the Team Chat channels where you want to use it, and make sure members can see the Slash Command that is actually configured
- Go to System Admin > Agent Management > Channels, and open Message Routing on the corresponding Zoom Team Chat channel
- Select the Default Agent/Team. You must configure the default before you enable group chat routing
- Add up to 19 rules as needed. For each rule, select an Agent/Team, fill in the required Command, and optionally add up to 10 keywords. Then turn on the enable switch and save
- Send
/ae +helpin the channel to verify the setup. If the actual Slash Command isn't/ae, replace it with the command the admin set
| Config items | Rule |
|---|---|
| Default Agent/Team | Must be configured before enabling; used when no command is specified and no keyword matches |
| Command | Required, 1–32 characters. Letters, digits, -, and _ are allowed, and system-reserved commands can't be used. Differences in letter case and full-width/half-width forms don't make commands distinct |
| Keywords | Optional. Up to 10 per rule, 2–32 characters each. When several keywords match, the longer keyword wins. If keywords of the same length can't be resolved uniquely, the default Agent/Team is used |
| Available options | You can select enabled and runnable system/company Agents, and Teams of the current company. Personal Agents don't appear among the candidates |
Usage in channels
The examples in the table below assume that the Slash Command configured in Zoom is /ae.
| Purpose | Example | Description |
|---|---|---|
| View available capabilities | /ae +help | Shows the capabilities that the current user can use and that can currently run |
| Specify an Agent/Team | /ae +analysis 分析本周数据 | analysis is a command configured by the admin |
| Route by keyword | /ae 帮我检查埋点方案 | Uses the matching rule when a keyword matches; otherwise uses the default |
| Cancel a task | /ae +cancel | The whole command must be sent exactly |
| Legacy syntax | /ae +agent analysis 分析本周数据 | Still supported, but using +analysis directly is recommended |
Command scope: Group chat routing doesn't support +new. Direct messages with the bot still support +new, +agent, and +cancel. Every new task in a channel must use the actual Slash Command.
Public context and personal data: Channel tasks use a separate new conversation and don't read direct messages with the bot or personal memories. Questions and answers in a channel are visible to channel members, so send sensitive information in a direct message with the bot.
6. FAQ
Credential verification fails
- Make sure that Client ID, Client Secret, Secret Token, Bot JID, and Account ID come from the same Zoom app environment
- Make sure that Chat Subscription is enabled for the Zoom app and that it includes the
imchat:botscope - Make sure that Development and Production credentials aren't mixed
Endpoint URL Validation fails
- Make sure that the Agentic Engine channel has completed Verify credentials and is enabled
- Make sure that the Bot Endpoint URL entered in Zoom exactly matches the address shown on the platform
- Make sure that Zoom can access the public HTTPS address of Agentic Engine
- Make sure that the Secret Token comes from the current Zoom app environment
Users can't bind their Zoom accounts
- Make sure that the binding code was sent with the actual Slash Command in a direct message with the bot
- Make sure that the binding code is still within its 10-minute validity period and hasn't been used
- Make sure that the Zoom account isn't bound to another Agentic Engine user
Bot doesn't receive channel messages
- Make sure that you're using a Zoom Slash Command, not a regular message or simply @mentioning the bot
- Make sure that the app has joined the target Team Chat channel. Being installed to the account or showing up in command suggestions doesn't mean the app has joined the channel
- Make sure that the user has completed account binding in a direct message with the bot
Slash Command disappears after sending
- Zoom doesn't show Slash Commands as regular channel messages. This is expected
- Wait a moment. The bot sends a message that includes the asker, the original question, and the answer
Bot receives commands but can't reply
- Make sure that the Bot JID, Account ID, and
imchat:botscope are configured correctly - Make sure that the channel is still enabled and that the app is still within the installation or test scope of the current Zoom account
Related pages and next steps
- See the setup instructions for other platforms: Channel management.
- Learn about the overall flow of channel connection and binding: Channel overview and binding.
- Configure the Agent to use: Agent.
- See how to use conversations in the platform: Conversations.