> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wednesdayai.dev/llms.txt
> Use this file to discover all available pages before exploring further.
# Channel setup
> Connect WednesdayAI to messaging platforms: WhatsApp, Telegram, iMessage, Signal, Slack, Discord, Teams, Matrix, and more.
# Channel setup
WednesdayAI connects to messaging platforms through channels. Each channel handles incoming messages, outgoing replies, and account pairing. Several channels are built in; others ship as plugins you install separately.
## Available channels
Personal and business WhatsApp via the linked-device protocol
Telegram bot — full Bot API support
iMessage via BlueBubbles (recommended) or legacy imsg
Signal via signal-cli
Slack app — Socket Mode or HTTP Events API
Discord bot via the Bot API and Gateway
Teams via Bot Framework (plugin)
Matrix/Element, with E2EE support (plugin)
WednesdayAI supports around twenty channels in total. Beyond those above, plugins exist for Feishu/Lark, Google Chat, IRC, LINE, Mattermost, Nextcloud Talk, Nostr, Synology Chat, Tlon, Twitch, Zalo, and Zalo Personal. The built-in Web chat needs no setup.
## General setup flow
Every channel follows the same pattern:
1. **Install the plugin** (only for non-bundled channels — Teams, Matrix, and others)
2. **Authenticate** — login wizard, bot token, or QR
3. **Configure access policies** — who can talk to the bot
4. **Pair** the channel to your agent
5. **Test** with a message
```bash theme={"dark"}
openclaw channels list # see installed channels
openclaw channels login --channel # authenticate
openclaw channels status --channel # check connectivity
```
## Access policies
After connecting a channel, configure who can interact with the agent. The DM policy is set **per channel** under `channels..dmPolicy`:
```json5 theme={"dark"}
{
channels: {
whatsapp: {
enabled: true,
dmPolicy: "allowlist", // pairing | allowlist | open | disabled
allowFrom: ["+15555550123"],
},
telegram: {
enabled: true,
botToken: "",
dmPolicy: "pairing",
},
},
}
```
| Policy | Effect |
| ------------------- | ------------------------------------------------------------------- |
| `pairing` (default) | New senders get a one-time pairing code; ignored until approved |
| `allowlist` | Only `allowFrom` entries can initiate — requires at least one entry |
| `open` | All senders accepted — requires `allowFrom: ["*"]` |
| `disabled` | DMs not accepted on this channel |
`channels.defaults` only accepts `groupPolicy` and `heartbeat`. Setting `dmPolicy` there will make the gateway refuse to start — configure it on each channel.
See [Security hardening](/admin/security) for the implications of each policy.
## Pairing
Most channels require pairing a specific account to the agent. New senders under `dmPolicy: "pairing"` receive a code; approve it:
```bash theme={"dark"}
openclaw pairing list
openclaw pairing approve
```
Pairing codes are 8 characters, expire after 1 hour, and are capped at 3 pending per channel. On subsequent startups the gateway reconnects automatically using stored credentials.
## Relinking
If a channel disconnects or credentials expire:
```bash theme={"dark"}
openclaw channels logout --channel
openclaw channels login --channel
```
## Channel logs
```bash theme={"dark"}
openclaw channels logs --channel --follow
```
## Per-channel guides