Actions21
- App Actions
- Table Actions
- View Actions
- Record Actions
- Field Actions
Overview
This node allows users to create a new table within a specified app in the Lark Suite Bitable service. It is useful for automating the management of tables in collaborative spreadsheets or databases hosted on Lark Suite, enabling workflows that require dynamic table creation based on input data or external triggers.
Common scenarios include:
- Automatically setting up new project tracking tables when a new project is initiated.
- Creating custom data collection tables for different departments or teams.
- Integrating with other systems to provision tables as part of onboarding or data import processes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: "Tenant Token" or "OAuth2". |
| App Token | The token identifying the specific Bitable app where the table will be created. |
| Table | Defines the table structure to create. Contains an array of items, each with a "name" property for columns or fields. |
| Custom Body | Allows specifying a fully custom JSON body for the request instead of using the standard "Table" property. Useful for advanced use cases or unsupported features. |
| Options > Use Custom Body | Boolean flag to toggle between using the standard "Table" property or providing a custom JSON body. |
Output
The node outputs JSON data representing the response from the Lark Suite API after creating the table. This typically includes details about the newly created table such as its ID, name, and metadata. No binary data output is involved.
Dependencies
- Requires valid authentication credentials via either a tenant token or OAuth2 token for Lark Suite API access.
- Needs the app token identifying the target Bitable app.
- The node communicates with the Lark Suite open API endpoint at
https://open.larksuite.com/open-apis.
Troubleshooting
- Invalid App Token: If the app token is incorrect or missing, the API will reject the request. Ensure the token corresponds to an existing Bitable app.
- Authentication Errors: Using wrong or expired tokens will cause authentication failures. Refresh or reconfigure credentials as needed.
- Malformed Table Definition: When not using a custom body, ensure the table items are correctly structured with valid names.
- Custom Body Issues: If using a custom JSON body, invalid JSON or incorrect schema may cause API errors. Validate JSON format and refer to Lark Suite API docs for correct structure.