Description
The code at remote_server.py:538-612 handles card.action.trigger events for interactive card button clicks, but this event type does not exist in the Lark Open Platform's event subscription list.
Problem
# Line 538-539
elif event_type == "card.action.trigger":
action = event.get("action", {})
However, according to Lark documentation and the user's investigation, card.action.trigger is NOT available as a subscribable event in Lark Open Platform.
Impact
All interactive card button functionality is broken:
- Confirmation buttons won't work
- Action selection buttons won't work
- The entire Minutes processing flow that relies on buttons is non-functional
Investigation Needed
- Research the correct way to handle card action callbacks in Lark
- Check if there's an alternative mechanism (possibly direct HTTP callback URL)
Possible Solutions
Option 1: Use Card Callback URL
Interactive cards may use a different callback mechanism. The card configuration might need a callback_url property:
{
"config": {
"wide_screen_mode": true
},
"callback": {
"url": "https://your-server.com/webhook/card_action"
}
}
Option 2: Use Message Card v2 API
Lark may have a different API for handling card interactions. Need to research:
Option 3: Use Bot Commands Instead
Replace button-based flow with text command flow:
- User sends: "議事録 タスク抽出"
- Bot responds with results directly
Priority
HIGH - Core interactive functionality is broken
Description
The code at
remote_server.py:538-612handlescard.action.triggerevents for interactive card button clicks, but this event type does not exist in the Lark Open Platform's event subscription list.Problem
However, according to Lark documentation and the user's investigation,
card.action.triggeris NOT available as a subscribable event in Lark Open Platform.Impact
All interactive card button functionality is broken:
Investigation Needed
Possible Solutions
Option 1: Use Card Callback URL
Interactive cards may use a different callback mechanism. The card configuration might need a
callback_urlproperty:{ "config": { "wide_screen_mode": true }, "callback": { "url": "https://your-server.com/webhook/card_action" } }Option 2: Use Message Card v2 API
Lark may have a different API for handling card interactions. Need to research:
Option 3: Use Bot Commands Instead
Replace button-based flow with text command flow:
Priority
HIGH - Core interactive functionality is broken