Feishu Interactive Card

When to Use

• Morning briefings (confirm/adjust/add task buttons)
• Evening reviews (acknowledge/defer buttons)
• Alert notifications (auto-fix/ignore/escalate buttons)
• Skill test results (listen/retest/mark-stable buttons)
• Any yes/no or multi-choice confirmation
• Status updates that need acknowledgment

Sending a Card

API

POST /open-apis/im/v1/messages?receive_id_type=chat_id

{
  "receive_id": "<chat_id>",
  "msg_type": "interactive",
  "content": "<card_json_string>"
}

content

Card Structure

{
  "config": { "wide_screen_mode": true },
  "header": {
    "title": { "tag": "plain_text", "content": "Card Title" },
    "template": "blue"
  },
  "elements": [
    { "tag": "div", "text": { "tag": "lark_md", "content": "**Bold** and `code` supported" } },
    { "tag": "hr" },
    { "tag": "action", "actions": [
      { "tag": "button", "text": { "tag": "plain_text", "content": "Confirm" }, "type": "primary", "value": { "action": "confirm" } },
      { "tag": "button", "text": { "tag": "plain_text", "content": "Adjust" }, "type": "default", "value": { "action": "adjust" } }
    ]}
  ]
}

Header Templates (Colors)

blue

green

red

orange

purple

turquoise

grey

Supported Elements

div

lark_md

hr

action

button

action

select_static

note

column_set

img

lark_md

Syntax

lark_md

• **bold**

  ,

  *italic*

  ,

  ~~strikethrough~~

• [link text](url)

• <at id=ou_xxx>name</at>

  for mentions
• Newlines: use

  \n

  within the string

Card Templates

Morning Briefing Card

1. Header: date + greeting (template: blue)
2. Section 1: Anomalies (red text if any, green "No anomalies" if clear)
3. Section 2: Today's action queue (numbered list with priority tags)
4. Section 3: Action buttons (Confirm / Adjust / Add Task)
5. Footer: generation timestamp

Alert Card

1. Header: alert type + service name (template: red)
2. Body: What happened, impact assessment
3. Action buttons (Auto-fix / Ignore / Escalate)

Skill Test Result Card

1. Header: skill name + pass/fail (template: green/red)
2. Body: Test metrics, pass count, details
3. Action buttons (Retest / Mark Stable / Archive)

Confirmation Card

{
  "header": { "title": { "tag": "plain_text", "content": "Confirmation Required" }, "template": "orange" },
  "elements": [
    { "tag": "div", "text": { "tag": "lark_md", "content": "**Question**: Description of what needs confirming" } },
    { "tag": "action", "actions": [
      { "tag": "button", "text": { "tag": "plain_text", "content": "Yes, proceed" }, "type": "primary", "value": { "action": "confirm", "context": "unique_id" } },
      { "tag": "button", "text": { "tag": "plain_text", "content": "No, cancel" }, "type": "danger", "value": { "action": "cancel", "context": "unique_id" } }
    ]}
  ]
}

Handling Callbacks

STATUS (2026-02-10): WebSocket currently does NOT subscribe to

card.action.trigger

events. Buttons on cards are display-only for now. Use the text fallback approach below until card callback support is added.

Current Approach: Text Fallback

1. Include clear text instructions in the card footer: "Reply '确认' to confirm, '调整' to adjust, '加任务' to add"
2. User replies with a text message → AI agent receives via

   im.message.receive_v1

   (works today)
3. Parse the text reply to determine the action

Future: Full Card Callbacks (when

card.action.trigger

is supported)

card.action.trigger

• action.value

  : The

  value

  object from the button definition

• operator.open_id

  : Who clicked

• token

  : For response verification

1. Parse

   action.value

   to determine what was clicked
2. Execute the corresponding action (e.g., mark today-actions as confirmed)
3. Update the original card to reflect the new state (e.g., change button to "Confirmed" checkmark)
4. Optionally send a brief follow-up message

PATCH /open-apis/im/v1/messages/:message_id

Best Practices

• One primary action: Each card should have one obvious primary button (type:

  primary

  ) and secondary options
• Value context: Always include enough context in button

  value

  to reconstruct what the button is about (e.g., date, task_id)
• Concise content: Cards are for quick scanning. Keep text short. Use

  lark_md

  formatting for emphasis.
• No walls of text: If content is long, summarize in card and link to a Feishu doc for details
• Template colors: Match the header color to the sentiment (red=alert, green=success, blue=info)

Dependencies

• Feishu IM API (POST messages with

  msg_type: interactive

  )
• WebSocket connection (receives

  card.action.trigger

  events)
• See

  FEISHU_API_HANDBOOK.md

  API #4 for interactive card details

Integration Points

• daily-briefing

  skill: Sends briefing as card instead of plain text

• ops-rhythm

  skill: Evening review uses card format

• n8n-ops

  skill: Alerts sent as red cards

• skill-lab

  skill: Test results sent as cards

• feishu-sync

  skill: Triggers sync after card confirmation