lark-base

To manage Feishu Base tables with lark-cli, you must read the matching reference document first, fetch table and field metadata using the base token, and follow prescribed naming conventions before executing any base commands.

Configuring formula and lookup fields in Feishu Base requires reading the detailed field property references first, fetching current table structures, and applying CLI guardrails to ensure expressions match documented schema requirements.

Yes, you can use lark-cli to automate workflows and configure dashboards by referencing the provided workflow schema and dashboard block configuration guides before enabling or modifying any Base automations.

Yes, lark-cli requires you to fetch table and field metadata first using commands like base +table-get with the target base token, ensuring you never guess table names or field structures before updating records.

When changing role permissions in Feishu Base, safety guardrails mandate reading the specific reference documents for role management, verifying base tokens and table IDs, and following prescribed priority rules before emitting permission commands.

lark-cli base commands fail when editing attachment fields if you skip the reference-driven workflow, which requires checking field properties and record value documentation before attempting to upload attachments or modify field configurations.