OpenClaw Feishu Base
Use this plugin when working with Feishu Base / Bitable in OpenClaw.
What it provides
A unified tool:
Recommended actions include:
- - INLINECODE1
- INLINECODE2
- INLINECODE3
- INLINECODE4
- INLINECODE5
- INLINECODE6
- INLINECODE7
- INLINECODE8
- INLINECODE9
- INLINECODE10
- INLINECODE11
- INLINECODE12
- INLINECODE13
- INLINECODE14
- INLINECODE15 (including linked fields via
link.table_id / link.table_name, plus duplex links via link.back_field_name) - INLINECODE19
- INLINECODE20
- INLINECODE21
- INLINECODE22
Best-use guidance
- - Prefer direct Base links or explicit identifiers (
app_token, table_id) when available. - Discovery helpers are convenience features; direct link/token workflows are more reliable.
- Inspect schema before writing when field names are uncertain.
- Query/list before update when locating existing records.
Safety
Destructive operations are supported but should be disabled by default unless explicitly needed.
Config flag:
- -
allowDelete: false (recommended default)
When deletion is disabled, destructive actions should be blocked:
- - INLINECODE26
- INLINECODE27
- INLINECODE28
Requirements
- - OpenClaw with Feishu channel configured
- valid Feishu credentials already present in OpenClaw config
- access to the target Base/Bitable resources
Notes
- - This plugin works best as a link-first / token-first Feishu Base tool.
- Some discovery flows depend on what Feishu APIs expose in the current tenant/account context.
- For field creation and schema mutation, prefer serialized one-by-one writes. Parallel field creation can hit Feishu-side limits and cause intermittent
400 failures. - Credential resolution prefers explicit
account_id, then active runtime/session account context when available, then runtime-injected channels.feishu, and finally persisted OpenClaw config from OPENCLAW_CONFIG_PATH or ~/.openclaw/openclaw.json when some runtime paths do not inject Feishu config consistently.
OpenClaw 飞书多维表格
在 OpenClaw 中处理 飞书多维表格 / Bitable 时使用此插件。
提供功能
统一工具：
推荐操作包括：
- - resolvelink
- listbases
- findtable
- listtables
- gettable
- getrecord
- queryrecords
- createrecords
- updaterecords
- upsertrecords
- deleterecords
- createtable
- renametable
- deletetable
- createfield（支持通过 link.tableid / link.tablename 创建关联字段，以及通过 link.backfieldname 创建双向关联）
- renamefield
- updatefield
- deletefield
- list_folder
最佳实践
- - 优先使用直接的多维表格链接或明确的标识符（apptoken、tableid）。
- 发现辅助功能为便利特性；直接链接/令牌工作流更可靠。
- 当字段名称不确定时，在写入前检查模式。
- 在更新前先查询/列出，以定位现有记录。
安全性
支持破坏性操作，但除非明确需要，否则应默认禁用。
配置标志：
- - allowDelete: false（推荐默认值）
当删除功能禁用时，应阻止破坏性操作：
- - deleterecords
- deletefield
- delete_table
要求
- - 已配置飞书渠道的 OpenClaw
- OpenClaw 配置中已存在有效的飞书凭证
- 可访问目标多维表格/Bitable 资源
注意事项
- - 此插件最适合作为链接优先/令牌优先的飞书多维表格工具。
- 部分发现流程取决于当前租户/账户上下文中飞书 API 暴露的内容。
- 对于字段创建和模式变更，建议串行逐条写入。并行创建字段可能触发飞书侧限制，导致间歇性 400 错误。
- 凭证解析优先使用明确的 accountid，其次是可用的运行时/会话账户上下文，然后是运行时注入的 channels.feishu，最后是当某些运行时路径未一致注入飞书配置时，从 OPENCLAWCONFIG_PATH 或 ~/.openclaw/openclaw.json 中持久化的 OpenClaw 配置。
