Messaging channels

T-Agent can connect to Telegram, Feishu or Lark, DingTalk, WeChat, and WeCom. Slack and Discord are currently marked as coming soon.

General setup

1. Open Settings > Channel configuration, select a channel, and read its field descriptions.
2. Create or select a bot or app in the channel's official administration console. Enter credentials only in the controlled configuration page, never in a chat, screenshot, document, or task instruction.
3. Select the agent, permitted users, primary chat, or allowed groups, then save and enable the channel.
4. Send a test message without sensitive information. Check access boundaries, group trigger rules, and notifications.
5. Disable the channel and revoke old credentials when staff change, a device is lost, a bot is replaced, or credentials may have leaked. Check scheduled-task dependencies first.

Telegram

Create a bot with BotFather and enter its Bot Token. The token controls the bot. Regenerate it immediately if exposed. A user usually needs to message the bot before a private conversation can begin. For group use, review privacy mode and mention requirements.

Official references: BotFather and Telegram bots, group privacy mode.

Feishu and Lark

Bind an existing bot by QR code or enter its App ID and App Secret. Confirm that the app belongs to the correct tenant and configure its availability, event subscription, and message permissions in the official console.

Test direct messages, group messages, notifications, and revoked access in a test group before production use.

Official references: Feishu custom app guide, Lark custom app guide.

DingTalk

Enter the Client ID or AppKey and Client Secret or AppSecret required by the selected DingTalk connection method. Enable the bot and the corresponding event or Stream configuration in the DingTalk developer console. Limit application visibility to the people who need it.

Official reference: DingTalk custom bot access.

WeChat

WeChat usually connects through a QR code or a login flow shown in the channel page. Use an authorized business account instead of a personal primary account. Login expiration, mobile confirmation, risk controls, and account changes can interrupt messages.

WeCom

An administrator normally creates an application and supplies the Corp ID, Agent ID, and Secret. A callback setup also requires a matching Token, EncodingAESKey, and callback URL. Keep every value within the same company and application, and limit visibility to the required departments.

Official references: create an app and obtain credentials, receive messages and events.