← Back to OpenClaw guide
Category 3

Channels and integrations

This lane covers where OpenClaw shows up, how it sends or receives work, and how browser-based operator flows fit into that picture.

Use this whenYou are wiring OpenClaw into Discord, Telegram, Slack, browser workflows, local previews, or message delivery paths.
Messaging surfaces

Choose the delivery lane that matches the real job

Most people do not need every channel. They need the one that fits the communication pattern: public team discussion, private direct replies, or lightweight operational updates. Start with the surface, not the brand list.

Discord

Best when channel visibility, public replies, and group context matter.

Telegram and Slack

Best when you want lighter chat integration or team workflow fit.

WhatsApp and Matrix

Use when direct communication or bridge-style setups matter more than broad feature depth.

Browser work

Use the browser as an operator surface, not a side quest

The browser matters when the task depends on a real logged-in session, visual QA, local preview inspection, or multi-step UI actions. It should support real operator work, not become an unstructured click safari.

Operator guidance

The patterns that prevent reply and routing mistakes

Most integration pain is not installation pain. It is reply-placement pain, permission pain, or unclear routing. Make sure the answer appears in the right visible place and that the workflow matches the room you are operating in.

Open the deeper reference links for this category