多维表格工作流，发送飞书消息只有1.0版本

[CSerht]

多维表格工作流，发送飞书消息，只有1.0版本，不支持2.0版本

[91-enjoy]

Hi @CSerht , thanks for the feedback! Just to clarify — when you mention that the Base workflow only supports "1.0" and not "2.0" when sending Feishu messages, are you referring to interactive cards (Card 2.0) specifically?

If so, great news: Card 2.0 message support has already landed! 🎉

We shipped a complete Card 2.0 creation and delivery system in #1688 (merged to main on 2026-07-02), covering 27 Card 2.0 components (column_set, form, button, input, select_*, date_picker, markdown, chart, table, etc.), a structured 7-step card creation workflow, P0–P7 quality guardrails, and native --msg-type interactive integration in im +messages-send / im +messages-reply.

If you were referring to something else (e.g., plain text messages or message templates in the workflow), feel free to share more details and we'll dig in. Thanks again for raising this!

[CSerht]

Hi @CSerht , thanks for the feedback! Just to clarify — when you mention that the Base workflow only supports "1.0" and not "2.0" when sending Feishu messages, are you referring to interactive cards (Card 2.0) specifically?

If so, great news: Card 2.0 message support has already landed! 🎉

We shipped a complete Card 2.0 creation and delivery system in #1688 (merged to main on 2026-07-02), covering 27 Card 2.0 components (column_set, form, button, input, select_*, date_picker, markdown, chart, table, etc.), a structured 7-step card creation workflow, P0–P7 quality guardrails, and native --msg-type interactive integration in im +messages-send / im +messages-reply.

If you were referring to something else (e.g., plain text messages or message templates in the workflow), feel free to share more details and we'll dig in. Thanks again for raising this!

我手动在工作流创建了发送飞书消息节点，它是2.0版本，随便填充了数据并保存工作流，让codex帮我更新具体的消息内容，它更新完成后，就变成了1.0版本了。

[91-enjoy]

多维表格工作流，发送飞书消息，只有1.0版本，不支持2.0版本

Hi @CSerht , thanks for the feedback! Just to clarify — when you mention that the Base workflow only supports "1.0" and not "2.0" when sending Feishu messages, are you referring to interactive cards (Card 2.0) specifically?
If so, great news: Card 2.0 message support has already landed! 🎉
We shipped a complete Card 2.0 creation and delivery system in #1688 (merged to main on 2026-07-02), covering 27 Card 2.0 components (column_set, form, button, input, select_*, date_picker, markdown, chart, table, etc.), a structured 7-step card creation workflow, P0–P7 quality guardrails, and native --msg-type interactive integration in im +messages-send / im +messages-reply.
If you were referring to something else (e.g., plain text messages or message templates in the workflow), feel free to share more details and we'll dig in. Thanks again for raising this!

我手动在工作流创建了发送飞书消息节点，它是2.0版本，随便填充了数据并保存工作流，让codex帮我更新具体的消息内容，它更新完成后，就变成了1.0版本了。

Thanks for the additional context! Just to make sure I understand the issue correctly:

1. You manually created a Card 2.0 message node in the workflow, filled in some placeholder data, and saved it.
2. When you used Codex to update the card content, the node was downgraded to Card 1.0.

Is that accurate? If so, this should already be fixed — Codex now has full Card 2.0 support via #1688, which has been merged to main. You can pick it up with:

lark-cli update       

Give it a try and let us know if the issue persists. Thanks again for reporting!

[CSerht]

多维表格工作流，发送飞书消息，只有1.0版本，不支持2.0版本

Hi @CSerht , thanks for the feedback! Just to clarify — when you mention that the Base workflow only supports "1.0" and not "2.0" when sending Feishu messages, are you referring to interactive cards (Card 2.0) specifically?
If so, great news: Card 2.0 message support has already landed! 🎉
We shipped a complete Card 2.0 creation and delivery system in #1688 (merged to main on 2026-07-02), covering 27 Card 2.0 components (column_set, form, button, input, select_*, date_picker, markdown, chart, table, etc.), a structured 7-step card creation workflow, P0–P7 quality guardrails, and native --msg-type interactive integration in im +messages-send / im +messages-reply.
If you were referring to something else (e.g., plain text messages or message templates in the workflow), feel free to share more details and we'll dig in. Thanks again for raising this!

我手动在工作流创建了发送飞书消息节点，它是2.0版本，随便填充了数据并保存工作流，让codex帮我更新具体的消息内容，它更新完成后，就变成了1.0版本了。

Thanks for the additional context! Just to make sure I understand the issue correctly:

1. You manually created a Card 2.0 message node in the workflow, filled in some placeholder data, and saved it.
2. When you used Codex to update the card content, the node was downgraded to Card 1.0.

Is that accurate? If so, this should already be fixed — Codex now has full Card 2.0 support via #1688, which has been merged to main. You can pick it up with:

lark-cli update
Give it a try and let us know if the issue persists. Thanks again for reporting!

我进一步检查了当前 main（package version 1.0.76），这个问题仍然不在 #1688 的覆盖范围内。

shortcuts/base/** 或 skills/lark-base/**。

目前 lark-base-workflow-schema.md 仍只定义了
LarkMessageAction，而 base +workflow-update 会对整个 workflow
的 steps 执行 PUT 替换。

因此以下场景仍会发生：

1. 在 Base UI 中手动创建“发送飞书消息 2.0”节点并保存。
2. 让 Codex 只修改该节点的消息内容。
3. Codex 根据现有 lark-base schema 重建 LarkMessageAction。
4. 原来的 2.0 节点被静默降级为 1.0。

期望行为：

• workflow-get 和 lark-base skill 能识别并完整保留消息 2.0 节点；
• 只修改文案时进行最小变更，不重建或降级节点；
• 增加 round-trip 回归测试：2.0 节点读取、修改内容、写回后仍为 2.0；
• 如果 Base Workflow OpenAPI 尚未公开 2.0 节点结构，应阻止不安全的
  workflow-update，并明确提示暂不支持，而不是静默转成 1.0。

请确认 Base 工作流“发送飞书消息 2.0”是否已有可用的 OpenAPI step
类型和 schema；如果有，希望补充到 lark-base workflow schema 中。