Skip to content

Feature Request: Add Feishu Interactive Card Parsing Support #48281

@rocky2046

Description

@rocky2046

Feature Request

Is your feature request related to a problem? Please describe.

Currently, the Feishu plugin can send interactive cards successfully, but cannot read/parse the content of received interactive cards. When a user sends an interactive card message, the bot only sees [Interactive Card] placeholder instead of the actual card content (header, elements, buttons, etc.).

Describe the solution you'd like

Add support for parsing Feishu interactive card messages, including:

  1. Parse card structure: Extract header (title, template), elements (div, hr, img, button, etc.)
  2. Extract text content: Get text from all card elements in markdown format
  3. Parse interactive actions: Handle button clicks and form submissions
  4. Provide card metadata: Make card JSON available for advanced use cases

Describe alternatives you've considered

Currently using Feishu docs (docx) as an alternative, which can be read successfully. However, interactive cards are better for:

  • Weekly reports
  • Notifications
  • Interactive forms
  • Rich media messages

Additional context

Current status:

  • ✅ Send interactive cards: Working (sendCardFeishu function)
  • ❌ Read interactive cards: Not implemented

Technical details:

  • OpenClaw version: 2026.3.8
  • Feishu plugin location: extensions/feishu/src/
  • Related files: bot.ts, mention.ts, send.ts

Expected behavior:
When receiving an interactive card like:

{
  "msg_type": "interactive",
  "card": {
    "header": {"title": {"content": "Test Card"}},
    "elements": [{"tag": "div", "text": {"content": "Hello"}}]
  }
}

The bot should be able to access:

  • Card title: "Test Card"
  • Card content: "Hello"
  • Full card JSON for advanced parsing

Use Case

Weekly Report Workflow:

  1. User sends weekly report via interactive card
  2. Bot reads and analyzes the report
  3. Bot summarizes and provides feedback

This is currently blocked because the bot cannot read card content.


Priority: Medium-High (blocks rich message workflows)
Estimated effort: Medium (parsing logic + integration with message handling)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions