OpenClaw Feishu Base

Use this plugin when working with Feishu Base / Bitable in OpenClaw.

What it provides

A unified tool:

• - INLINECODE0

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.