Feature request: import local CSV/Excel into Base (Bitable)

[timzhong1024]

Summary

Add a command to import a local CSV or Excel file directly into Lark Base / Feishu Bitable.

Problem

lark-cli can create a Base, create tables/fields/records, and upload files to Drive, but it does not seem to provide a direct way to import a user's existing spreadsheet into Base.

For a common workflow, users already have data in .csv, .xlsx, or .xls and want to create a Base from that file without manually recreating schema and records.

Expected capability

Support something along these lines:

lark-cli base import --file ./data.csv
lark-cli base import --file ./data.xlsx --sheet Sheet1
lark-cli base import --file ./data.xlsx --base-name "My Base" --table-name "Sheet1"

Expected behavior

• Accept local CSV and Excel files
• Create a new Base, or import into an existing Base/table
• Infer columns and create matching fields automatically
• Import rows as records
• For Excel, allow selecting a sheet
• Provide a dry-run / preview mode before writing
• Return created base/table identifiers and URL

Why this matters

This is a very natural entry point for new users. "I have a spreadsheet, turn it into a Base" is one of the first tasks many users try.

Right now the workaround is to manually parse the file and then call base +table-create / base +record-upsert repeatedly, which is much more cumbersome than a single import command.

Possible scope

Even a first version that only supports CSV import into a newly created Base would already be very useful.

[zgz2048]

Thanks for the feature request. This is a very reasonable use case, and we agree that importing existing local spreadsheet data into Base should be much easier.

A quick update from our side: the JSON-based batch record import capability is already implemented, and we expect to ship it in the near term. In other words, the core path for bulk record import is already done on our side.

For Excel, CSV, and similar local file formats, the near-term plan is to have the agent use tools to parse and convert the file into the appropriate structured payload first, and then call the batch import capability to import the full dataset into Base.

So the direction here is:

1. Use tools to convert local spreadsheet content into structured data.
2. Use the batch import capability to write all records into Base efficiently.

We’ll share another update on this issue when the user-facing workflow is ready.