openclaw - 💡(How to fix) Fix Feature Request: Feishu plugin support for card.action.trigger event [1 participants]

Summary

The bundled Feishu plugin currently supports im.message.receive_v1 events via WebSocket but does not handle card.action.trigger callback events. When a user clicks an interactive card button (e.g., approve/reject/complete), the event arrives at the WebSocket connection but is silently dropped because no handler is registered.

Use Case

We use OpenClaw gateway on multiple nodes (skynet-alpha, able-cc) with Feishu bots for team collaboration. Our central PROD server sends interactive task cards to team members via Feishu. When a member clicks "Complete" or "Reject", we need the callback to be processed — either locally by the gateway or forwarded to the central server.

Current workaround: We created a separate dedicated Bot (AetherOS Task Bot) whose WebSocket is held exclusively by PROD, bypassing the per-node gateway entirely. This works but adds unnecessary complexity.

Expected Behavior

The Feishu plugin should:

1. Register card.action.trigger in the EventDispatcherHandler (alongside im.message.receive_v1)
2. When a card action event arrives, either:
   • a. Dispatch it to the agent session (like a message), or
   • b. Forward it via a configurable hook/webhook, or
   • c. Write it to a local file (e.g., inbox) for external processing

Option (a) would be ideal — the agent could process the callback and respond.

Environment

• OpenClaw version: latest (homebrew)
• Feishu plugin: bundled (dist/plugin-sdk/feishu.js)
• Connection mode: WebSocket
• OS: macOS (Apple Silicon)

Evidence

Gateway log shows message events are dispatched but card action events produce no log at all:

[feishu] feishu[default]: received message from ou_xxx in oc_xxx (p2p)
[feishu] feishu[default]: dispatching to agent (session=agent:main:feishu:direct:ou_xxx)
[feishu] feishu[default]: dispatch complete (queuedFinal=true, replies=1)
// No log for card.action.trigger — event silently dropped

The lark-oapi SDK fully supports this event type via register_p2_card_action_trigger.

Impact

This affects any deployment where:

• Interactive cards are sent through a Feishu bot managed by OpenClaw gateway
• Card button callbacks need to be processed (approve/reject/complete workflows)
• Multi-node setups where the card sender and callback receiver may be different nodes

Thank you for considering this enhancement.