Integrations
Channels
Connect agents to web chat, Telegram, Discord, Slack, WeChat, LINE, and Feishu.
Channels let end users talk to agents outside the built-in dashboard. Each channel binding belongs to an agent and isolates sessions by channel and external chat/user ID.
Supported Channels
| Channel | Endpoint family | Notes |
|---|---|---|
| Web | /agents/{id}/chat/ | Built-in web chat |
| Telegram | /api/agents/{id}/channels/telegram | Validates bot token with getMe |
| Discord | /api/agents/{id}/channels/discord | Validates bot token with /users/@me |
| Slack | /api/agents/{id}/channels/slack | Validates token with auth.test |
/api/agents/{id}/channels/wechat/login | QR/session login flow | |
| LINE | /api/agents/{id}/channels/line | Webhook at /api/line/webhook/{accountId} |
| Feishu | /api/agents/{id}/channels/feishu | Webhook at /api/feishu/webhook/{appId} |
Channel Management API
GET /api/agents/{id}/channels
POST /api/agents/{id}/channels/telegram
POST /api/agents/{id}/channels/discord
POST /api/agents/{id}/channels/slack
POST /api/agents/{id}/channels/wechat/login
GET /api/agents/{id}/channels/wechat/login/status
POST /api/agents/{id}/channels/line
POST /api/agents/{id}/channels/feishu
PATCH /api/agents/{id}/channels/{type}/{accountId}
DELETE /api/agents/{id}/channels/{type}/{accountId}Session Isolation
FastClaw stores channel sessions separately from dashboard chat sessions. A Telegram user and a Discord user talking to the same agent do not share session memory unless your application explicitly maps them to the same user context.
Operational Notes
- For public web chat, enable the agent's
Public accesstoggle. - For IM channels, use stable bot/account IDs as account identifiers.
- Configure external webhook URLs to point at the deployed FastClaw gateway.
- If multiple gateway pods are running, use Redis-backed leases so one worker owns each channel connection.