Actions21
- App Actions
- Table Actions
- View Actions
- Record Actions
- Field Actions
Overview
This node is designed to delete a specific field from a table within a "bitable" app in the Lark Suite environment. It is useful when you need to programmatically remove fields (columns) from a database-like table managed in Lark's Docs Bitable service. Common scenarios include cleaning up unused or obsolete fields, automating schema changes, or managing dynamic data structures.
For example, if you have an automated workflow that manages project data and a certain field is no longer relevant, this node can be used to delete that field automatically without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: Tenant Token, OAuth2 |
| App Token | The token identifying the bitable app where the table resides. Can be selected from a list or entered as an ID string. |
| Table Id | The identifier of the table containing the field to delete. |
| Field Id | The identifier of the field to be deleted from the specified table. |
| Options | Additional options for the request: |
| - Use Custom Body | Boolean flag indicating whether to use a custom request body instead of the default one. |
Output
The node outputs JSON data representing the response from the Lark Suite API after attempting to delete the field. This typically includes status information about the deletion operation, such as success confirmation or error details.
No binary data output is involved in this operation.
Dependencies
- Requires authentication via either a Tenant Token or OAuth2 credentials configured in n8n.
- Depends on access to the Lark Suite Docs Bitable API endpoint (
https://open.larksuite.com/open-apis). - Requires valid
app_token,table_id, andfield_idvalues corresponding to existing resources in Lark Suite.
Troubleshooting
- Invalid App Token, Table Id, or Field Id: Ensure these IDs are correct and correspond to existing resources. Errors will occur if any ID is invalid or does not exist.
- Authentication Failures: Verify that the provided authentication method (Tenant Token or OAuth2) is correctly set up and has sufficient permissions.
- API Rate Limits or Network Issues: Temporary failures may happen due to rate limiting or connectivity problems; retrying later might help.
- Use Custom Body Option: If enabled incorrectly, it may cause malformed requests leading to errors. Only enable if you intend to provide a custom request payload.
Common error messages usually come directly from the Lark Suite API and indicate issues like unauthorized access, resource not found, or invalid parameters.