Connect Feishu Bitable

The Feishu Bitable connector imports one table view as a refreshable dataset. It uses a Feishu custom app, not a person's Feishu password.

Before you start

You must be a workspace Owner or Collaborator.
Your plan must include the Feishu connector.
You need a Feishu custom app with an App ID and App Secret.
Grant the app permission to read Bitable records.
Add the app to the target Bitable as a readable document collaborator. If advanced permissions are enabled, also add it to a role that can read the target table.

The App Secret is encrypted when saved and is not shown again.

1. Create the Feishu connection

Open Data.
Choose Add → Connection → Feishu Bitable.
Enter a connection name, the custom app's App ID, and App Secret.
Save the connection.

If you later edit the connection, leave the App Secret blank to keep the saved secret. Enter a new value only when rotating it.

2. Import a view

Find the Feishu connection and choose Import rows.
Paste the full Bitable URL. Luxiva AI extracts the App Token, table ID and view ID when they are present.
Alternatively, enter the identifiers manually:
- App Token is the value after /base/ in the URL.
- Table ID is optional when listing views.
- View ID requires a Table ID and can import that view directly.
Choose List views, select the view, and import it.
Review the proposed metrics.

The selected view matters: filtering or field visibility in Feishu can change which records and columns are imported.

Refresh and source ownership

Refreshing replaces the local snapshot with the current records from the same Bitable table and view. If refresh fails, Luxiva AI keeps the last successful snapshot.

Make durable corrections in Feishu. Connector refreshes replace local rows, so local cleaning is not a substitute for fixing the source.

Troubleshooting

Authentication failed

Check the App ID and re-enter the App Secret. Make sure both values belong to the same custom app.

The app cannot access this Bitable

In the Bitable, open … → More → Add document app, then add the custom app as a readable collaborator.

Access is still denied with advanced permissions

Open … → More → Advanced permissions and add the app to a role that can read the target table.

App Token not found

Paste the full Bitable URL, or enter only the value after /base/, such as bascnXXXXXXXX. Do not put the whole URL in the App Token field.

The source is empty

Confirm that the selected view contains visible records and columns that the app can read.