#channels.whatsapp.enabled unknown key

1 messages · Page 1 of 1 (latest)

hard plover
#

After upgrading to 2026.2.22-2 and it looks like move configuration for whatsapp to plugins, I pick up the unknown key error.
The Doctor doesn't fix it, just wondering proper way to migrate the settings?

drifting prismBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> âś… Mark Solution

limber ridge
#

set your whatsapp in terminal with openclaw config in channels section

#

then restart the gateway it will connect

hard plover
limber ridge
#

Yes config will fix openclaw.jsob

spare jackalBOT
#

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):