Reach · 08.02
Messaging Channels
Discord, Slack, Telegram, WhatsApp, and Voice — direction, threading, attachments, and the quirks of each.
Channels
One dispatcher, five very different transports
| Channel | Direction | Notes |
|---|---|---|
| Discord | Outbound | Multipart attachments. |
| Slack | Bidirectional | Threads, plus external-upload files. |
| Telegram | Bidirectional | Webhook or polling — a stray 409 usually means a gateway conflict, not a bug in your bot. |
| Bidirectional | Baileys QR link; voice-note transcription; peers are keyed off remoteJidAlt (the @lid form), not the plain JID. | |
| Voice | Webhook | Transcription in, TTS reply buffer out. |
Whichever transport delivers a message, it lands on the same universal chat harness — see Chat Sessions & the Universal Harness — so permission modes and turn behavior never vary by channel.
Continue
Connections: How Agents Reach People & Systems
The Connection primitive: peer identity resolved across channels, durable inbound queues, and rich two-way attachments.
Connections
Deterministic Channel Sends
A workflow reaches the world with a zero-token channel node — not an agent prompt — that resolves a connection, delivers, and returns a receipt SWIFT can verify.
ChannelsWorkflows