Actions21
- App Actions
- Table Actions
- View Actions
- Record Actions
- Field Actions
Overview
The node provides integration with Lark Suite's base management API, specifically focusing on managing tables within the "Bitable" app environment. The "List All Tables" operation under the "Table" resource allows users to retrieve a list of all tables associated with a specified Bitable app token.
This node is beneficial in scenarios where users need to programmatically access metadata about their Bitable apps, such as enumerating all tables for further processing or automation workflows. For example, it can be used to dynamically fetch table lists before performing data synchronization or reporting tasks.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: Tenant Token, OAuth2 |
| App Token | The unique token identifying the Bitable app whose tables are to be listed. Can be selected from a list or entered manually as an ID. |
| Options | Additional optional settings: - Use Custom Body (boolean): Whether to send a custom request body instead of default |
Output
The output JSON contains an array of table objects representing each table found in the specified Bitable app. Each table object typically includes metadata such as table ID, name, and other descriptive attributes provided by the Lark Suite API.
If the node supports binary data output, it would relate to any file or attachment data associated with tables, but based on the provided code and properties, this operation primarily outputs JSON metadata.
Dependencies
- Requires valid authentication via either a Tenant Token or OAuth2 credentials configured in n8n.
- Needs a valid Bitable app token to identify which app's tables to list.
- Connects to the Lark Suite Open APIs endpoint at
https://open.larksuite.com/open-apis.
Troubleshooting
- Invalid App Token: If the app token is incorrect or missing, the API will fail to return tables. Ensure the token matches the expected format (alphanumeric) and corresponds to an existing Bitable app.
- Authentication Errors: Using incorrect or expired credentials will result in authorization failures. Verify that the chosen authentication method is properly set up and tokens are valid.
- API Rate Limits: Frequent calls may hit rate limits imposed by Lark Suite. Implement retry logic or reduce call frequency if encountering rate limit errors.
- Custom Body Usage: Enabling "Use Custom Body" without proper formatting may cause request failures. Only enable this option if you intend to override the default request payload with a correctly structured body.