Channels

Channels Overview

Let your agent answer in WhatsApp, Telegram, Slack, Feishu, and more — channels route inbound messages to an agent and stream replies back.

Your agent is most useful where people already are — a WhatsApp thread, a Slack channel, a Feishu group, your own website. A channel connects one messaging surface to one Buda agent: it receives inbound messages, routes each conversation to the right chat session, and streams the agent's reply back. You set it up once; the connection stays alive in the background.

An agent answering live in a chat session

How a channel works

Every channel does the same four things, regardless of provider:

  • Receives inbound user messages from the connected platform.
  • Routes each user or group conversation to its own chat session, so context carries between turns.
  • Runs the target agent on the message and streams the reply back to the same thread.
  • Stays connected in the background — most providers use a persistent connection, so there's no webhook URL to host.

How a channel routes messages to an agent and streams replies back

Channels are scoped to you, not a single space: one account can connect several bots, each pointing a different space's agent at a different audience.

Pick a channel

How you connect depends on the provider. QR-based providers are scan-and-go; token providers need a bot token or app credentials from the platform's developer console.

ChannelBest forHow you connect
WhatsAppCustomer support, sales, lead captureScan a QR code (logs in as that account)
WeChatPersonal WeChat contacts in ChinaClawBot QR code or hosted account
TelegramBots, communities, internal automationBotFather token
DiscordDeveloper and community serversBot token (Gateway, no webhook)
SlackInternal team workflowsBot + app-level token (Socket Mode)
Microsoft TeamsEnterprise teams on TeamsAzure Bot app credentials
WeComChina-based company messagingSmart Bot or hosted account
DingTalkChina-based company messagingScan to auto-register, or Client ID + Secret (Stream Mode)
Feishu / LarkLark/Feishu collaborationApp ID + App Secret (WebSocket)
Web chat widgetYour own site or productGenerate an embed snippet

Before you connect

  • The target agent already exists. A channel points at one agent — create and test it first.
  • Drive is loaded. Upload the files the agent should reference so it answers from real context.
  • You've picked an audience. External customers, internal teammates, or both — this shapes your tone and escalation policy.
  • You start small. Connect one agent to one channel, validate the responses on real conversations, then add more.

Most providers connect over a persistent connection (Gateway or WebSocket), so you don't need to host a public webhook URL. Microsoft Teams is the exception — it uses a messaging endpoint.

Connect a channel

  • Chat session — how conversations map to sessions
  • Agents — create the agent a channel points to

On this page