🌏 中文版
Enterprise environments typically use Slack, Microsoft Teams, or self-hosted Matrix. This article covers the setup methods and characteristics of each channel.
Slack
OpenClaw has the most complete support for Slack, with two connection modes.
Socket Mode (Default)
- Enable Socket Mode in the Slack App settings
- Create an App Token (
xapp-..., scope:connections:write) - Install the app and obtain the Bot Token (
xoxb-...) - Configure both tokens and subscribe to bot events
- Start the Gateway
HTTP Mode
- Set
mode: "http" - Obtain the Signing Secret
- Configure the webhook path (default:
/slack/events) - Register Events/Interactivity/Slash commands URLs in Slack
Key Features
Native Streaming: After enabling Slack’s Agents and AI Apps feature, native streaming is supported (partial (default) / block / progress / off).
Native Slash Commands: Set commands.native: true, then register the corresponding commands in Slack. Note: /status is reserved by Slack; use /agentstatus instead.
Interactive Replies: When enabled, the agent can use Slack buttons and select menus.
Access Control
DM: pairing / allowlist / open / disabled. Channel: open / allowlist / disabled; mention required by default.
Troubleshooting
Channel access issue check order: policy → allowlist → mention → user restrictions.
DM issues: dm.enabled → policy → pairing approvals.
Diagnostics: openclaw channels status --probe + openclaw doctor.
Microsoft Teams
Teams is a plugin that requires separate installation.
openclaw plugins install @openclaw/msteams
Setup
Three Azure Bot credentials are required: App ID, App Password, and Tenant ID.
Workflow: Create Azure Bot resource → Set messaging endpoint → Enable Teams channel → Configure OpenClaw.
Features
| Feature | Support |
|---|---|
| DM | ✅ |
| Group chat | ✅ |
| Channel | ✅ |
| File attachments | ✅ (personal conversations) |
| Adaptive Cards | ✅ (polls, formatted content) |
| Message history | ✅ (configurable limit) |
Access Control
DM defaults to pairing. Group/Channel defaults to allowlist. It’s recommended to use stable Teams/Channel IDs rather than mutable display names.
Limitations
- Webhook timeout restrictions
- File sending in channels and groups requires SharePoint integration + Graph API permissions
- Downloading hosted images requires additional Microsoft Graph permissions
Google Chat
HTTP webhook integration with relatively simple setup. Configuration details are in docs/channels/googlechat.md.
Matrix
Matrix is a plugin with the most complete security features — including end-to-end encryption (E2EE).
openclaw plugins install @openclaw/matrix
Authentication Methods
Token-based (Recommended):
{
channels: {
matrix: {
enabled: true,
homeserver: "https://matrix.example.org",
accessToken: "syt_xxx",
dm: { policy: "pairing" }
}
}
}
Password-based: homeserver + userId + password + deviceName.
E2EE Encryption
{ encryption: true }
Management commands:
openclaw matrix verify status # Check verification status
openclaw matrix verify bootstrap # Set up cross-signing
openclaw matrix verify backup status # Backup status
openclaw matrix verify backup restore # Restore encrypted messages
openclaw matrix devices list # List devices
openclaw matrix devices prune-stale # Remove stale devices
“Verified” requires cross-signing (your identity signs it), not just local trust.
Thread Support
| Mode | Behavior |
|---|---|
off | Replies at top-level |
inbound | Uses threads only when receiving threaded messages |
always | Group replies always use threads |
Multiple Accounts
{
matrix: {
defaultAccount: "assistant",
accounts: {
assistant: { /* config */ },
alerts: { /* config */ }
}
}
}
Bot-to-Bot Communication
By default, messages from other OpenClaw Matrix accounts are ignored (preventing self-reply loops). Set allowBots: "mentions" to allow agents to interact via mentions.
Other Features
Reactions, Polls, Location sharing, media attachments, DM status repair (openclaw matrix direct repair), and private/LAN homeserver support.
Feishu
A plugin channel designed for Chinese enterprise environments. Configuration is in docs/channels/feishu.md.
Enterprise Channel Comparison
| Slack | Teams | Matrix | Google Chat | |
|---|---|---|---|---|
| Installation | Built-in | Plugin | Plugin | Built-in |
| Connection Mode | Socket / HTTP | Azure Bot | SDK | Webhook |
| DM | ✅ | ✅ | ✅ | ✅ |
| Group/Channel | ✅ | ✅ | ✅ (Room) | ✅ |
| Thread | ✅ | ✅ | ✅ | ❌ |
| E2EE | ❌ | ❌ | ✅ | ❌ |
| Native Streaming | ✅ | ❌ | ❌ | ❌ |
| Interactive | ✅ | Adaptive Cards | Reactions/Polls | ❌ |
| Multiple Accounts | ✅ | ✅ | ✅ | ✅ |
Summary
Slack is the most feature-complete enterprise channel — it has native streaming, slash commands, and interactive replies. Teams is more complex to set up but covers the Microsoft ecosystem. Matrix is ideal for teams that value privacy and self-hosting, with E2EE as its exclusive advantage.
References
This article is compiled from the following OpenClaw source documents:
- docs/channels/slack.md — Slack setup
- docs/channels/msteams.md — Microsoft Teams setup
- docs/channels/googlechat.md — Google Chat setup
- docs/channels/matrix.md — Matrix setup
- docs/channels/feishu.md — Feishu setup
Loading...