openclaw - 💡(How to fix) Fix Feishu card.action.trigger via WebSocket: parseFeishuCardActionEventPayload rejects valid payloads (missing user_id, context field mismatch) [1 participants]

Bug Description

When using Feishu WebSocket long-connection mode (connectionMode: "websocket"), clicking card buttons (interactive cards with action buttons) always results in:

feishu[<accountId>]: ignoring malformed card action payload

The card action is received by the gateway but parseFeishuCardActionEventPayload() returns null, so the callback is silently dropped.

Root Cause

parseFeishuCardActionEventPayload() in monitor-*.js requires all of these fields to be non-empty:

if (!token || !openId || !userId || !unionId || !tag || !isRecord(actionValue) || !contextOpenId || !contextUserId || !chatId) return null;

However, the Feishu WebSocket SDK delivers card.action.trigger payloads with a different field structure than the HTTP webhook callback:

Actual WebSocket payload (captured)

{
  "schema": "2.0",
  "event_type": "card.action.trigger",
  "operator": {
    "tenant_key": "xxx",
    "open_id": "ou_xxx",
    "union_id": "on_xxx"
  },
  "action": {
    "value": {"command": "some_value"},
    "tag": "button"
  },
  "context": {
    "open_message_id": "om_xxx",
    "open_chat_id": "oc_xxx"
  }
}

Note: operator.user_id, context.open_id, context.user_id, and context.chat_id are all absent. Only context.open_chat_id is provided (not context.chat_id).

Suggested Fix

In parseFeishuCardActionEventPayload(), use fallbacks for missing fields:

const userId = readString(operator.user_id) || openId;        // fallback to open_id
const contextOpenId = readString(context.open_id) || openId;   // fallback to operator open_id
const contextUserId = readString(context.user_id) || userId;   // fallback to userId
const chatId = readString(context.chat_id) || readString(context.open_chat_id);  // accept open_chat_id

// Relax the null check — userId and contextOpenId/contextUserId are now derived
if (!token || !openId || !unionId || !tag || !isRecord(actionValue) || !chatId) return null;

This maintains backward compatibility with HTTP webhook payloads while also supporting WebSocket payloads.

Impact

• All card button interactions via WebSocket mode are broken (100% failure rate)
• Only affects connectionMode: "websocket" — HTTP webhook mode is unaffected
• The gateway successfully receives the callback but silently drops it

Environment

• OpenClaw version: 2026.4.2
• Feishu SDK: lark-oapi (Python 1.5.3 / Node @larksuiteoapi/node-sdk)
• Connection mode: websocket
• OS: macOS (arm64)

Workaround

Manually patching parseFeishuCardActionEventPayload() in dist/monitor-*.js with the fallback logic above. This patch is lost on openclaw update.