Skip to main content

Channel management

Last updated 10/06/2026

Reading guide​

Parent section: Channels and Integrations.

Search keywords: Channel management, channel configuration, platform credentials, message permissions, event subscriptions.

See below for detailed instructions.

This document describes how to connect channels in Agentic Engine. With it, you can quickly integrate third-party channels with Agent services and enable message receiving, user interaction, and channel communication.

What channel management solves: It lets your team connect and maintain external chat entry points in one place, and configure channel instances and message routing so that business requests reach the right Agent or Team. Admins are responsible for platform apps and channel configuration, while users bind their own external accounts separately. Creating a channel doesn't complete binding for all members.

Who it's for: Admins with system management permissions. The management scope is the current company. If you don't see the channel entry or get a message that the feature is not enabled, contact your system admin to confirm that the permissions, the sandbox, and the channel feature are enabled.

You can configure Group Chat Message Routing for each Feishu/Lark tenant, Slack Workspace, Discord Server, DingTalk organization, WeCom organization, or Mattermost Site. Admins can set a default Agent/Team and route group chat tasks to different capabilities by command or keyword. For the permissions, configuration steps, and user commands that each platform requires, see the corresponding sub-guides above.

In message routing, Group Chat Space refers to the connection scope on the external platform, not an AE workspace. The admin's group chat routing configuration and a user's choice of workspace and Agent in regular direct messages are separate settings and can't replace each other.

warning

Connection checklist: Filling in the app credentials alone is not enough. Follow the sub-guide for each channel to complete message and file permissions, group chat event subscriptions, interaction callbacks, and version release or reinstallation. Otherwise, you may run into issues such as "direct messages work, but the bot can't be invoked in group chats" or "text works, but question forms, images, or generated files fail".

Instances and identities: One organization can configure multiple channel instances, but the same Bot identity can't be configured more than once in the same runtime environment. Also, don't connect the same Bot to multiple cluster environments at the same time. Otherwise, you may see duplicate consumption, duplicate replies, conversation drift, or cancel commands hitting the wrong task.

Configure channels in System Admin​

Admins maintain Feishu, Slack, and other channel instances in System Admin > Agent Management > Channels. Complete each platform's credential, permission, callback, and release steps by following the corresponding platform guide above.

Create and verify

  1. Click New Channel, enter a channel name that your team can easily recognize, and select a channel type. If a platform has multiple instances, use names that tell them apart. The channel type can't be changed after creation.
  2. Fill in the required credentials for the selected platform, set the default model, fill in Channel Input Suffix as needed, and save. The default model can reference the company default or the channel user's personal default, or you can select an available model from the list. This is not the same as selecting an Agent or configuring group chat routing.
  3. Confirm that the instance is enabled, and complete credential verification or linking for the platform. For supported instances, opening Message Routing checks the verification status first. For Zoom Team Chat, you can use Verify credentials. For WhatsApp, an admin needs to link the shared bot account by QR code after the channel is saved and enabled.
  4. After configuration, have users bind their personal accounts by following Channel overview and binding, and then verify the direct message, group chat, and file interactions you actually need. Successful credential verification doesn't mean that all permissions, event subscriptions, and interaction callbacks are configured correctly.

Configure group chat message routing

On the instance, open Message Routing, select the Group Chat Space to configure, set Enable group chat routing and Default Agent/Team, and then add the Agents/Teams that can be selected by command or keyword as needed. Each new target requires a Command, while keywords are optional. Before saving, resolve any duplicate-name, format, or quantity issues shown in the interface.

If no group chat space is available to configure, check the permissions, installation, and group chat event configuration by following the corresponding platform guide, and then come back here to check or verify again. Don't work around configuration issues by creating duplicate instances for the same Bot.

Maintenance notes

  • When you edit secrets, you don't need to re-enter fields marked leave empty to keep unchanged. A secret that isn't displayed again doesn't mean the configuration is lost.
  • Changing key credentials may invalidate the previous verification result and the group chat routing entry. When Confirm Configuration Change appears, check the affected users first. After you confirm, those users need to bind again, and you need to recheck the credential verification and group chat routing status.
  • Disable stops the instance from receiving and processing new messages. Delete also removes the user bindings under the instance and clears its group chat routing configuration. Deletion shows a warning that it can't be undone, so confirm the scope of impact first and don't use deletion as a regular disable.

Channel management

New Channel (Feishu)

New Channel (Slack)

Was this page helpful?
On this page