#channels.whatsapp.enabled unknown key
1 messages · Page 1 of 1 (latest)
i am getting the same error
set your whatsapp in terminal with openclaw config in channels section
then restart the gateway it will connect
It’s connecting I just see that message. Will config fix the openclaw.json? To set up the configuration in the new location?
Yes config will fix openclaw.jsob
channels.whatsapp.enabled is just not a valid config key anymore (config is now .strict()), so you’ll get “unknown key” until you remove it.
WhatsApp didn’t move to a different top-level config namespace — it’s still configured under channels.whatsapp, but the channel no longer has a root enabled flag. It “starts” when there’s a linked WhatsApp Web session (and you can effectively disable it via policy, or per-account enabled).
What to change in ~/.openclaw/openclaw.json (JSON5)
Before (old / now invalid):
{
channels: {
whatsapp: {
enabled: true, // ❌ remove this
},
},
}
After (typical minimal):
{
channels: {
whatsapp: {
dmPolicy: "pairing", // or "allowlist"
allowFrom: ["+15551234567"], // your number(s)
groupPolicy: "allowlist",
groupAllowFrom: ["+15551234567"],
},
},
}
If you’re using multi-account WhatsApp, the only enabled that exists is per-account:
{
channels: {
whatsapp: {
accounts: {
default: { enabled: true },
work: { enabled: false },
},
},
},
}
After editing
- restart (or let reload do it, but restart is simplest):
openclaw gateway restart
- then re-check:
openclaw channels status
Docs:
- WhatsApp channel config: https://docs.openclaw.ai/channels/whatsapp
- Config reference (WhatsApp section): https://docs.openclaw.ai/gateway/configuration-reference#whatsapp
If you paste your current channels.whatsapp { ... } block (redact phone numbers), I can point out any other keys that got renamed/removed in 2026.2.22-2.