Подключение отдельных каналов и документация

Before a chat app can reach OpenClaw, you pair it once through the Gateway. After that, messages flow without re-pairing.

No two apps connect the same way. Each platform has its own pairing flow, so the exact steps depend on the channel you pick.

Per-platform instructions live under the /channels/ docs. Each channel has its own page with the precise steps to follow.

Beyond the big names, OpenClaw also supports Teams, Google Chat, Matrix, Zalo, and Twitch, each with its own channel page.

The Microsoft Teams channel fits organizations on Microsoft's stack, letting OpenClaw join your existing Teams chats.

Google Chat covers Workspace users, and Matrix suits open, federated messaging. Both bridge through the same Gateway.

OpenClaw even reaches Zalo for regional messaging and Twitch for streaming chat, each documented on its own channel page.

Open the right channel page first and follow it step by step. Guessing the flow is the fastest way to a broken connection.

However different the steps look, every channel ends up registered with the same Gateway that routes your messages.

You do not need every platform. Pair just the channels you actually chat in and leave the rest until you need them.

Treat the /channels/ docs as your map for new platforms. When a connection stalls, the channel page is the first place to check. 🗺️

You learned that each platform pairs its own way via the /channels/ docs, covering Teams, Google Chat, Matrix, Zalo, and Twitch through one Gateway. ✅