Channels Overview

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.

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.

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.

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.

Connect a channel

Related

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