Actions21
- App Actions
- Table Actions
- View Actions
- Record Actions
- Field Actions
Overview
This node facilitates creating a new "View" in a Bitable (a table-like app) within the Lark Suite platform. It is useful for users who want to programmatically manage and customize views of their data tables, such as filtering or sorting data presentation without manual intervention.
Typical use cases include:
- Automating the creation of custom views for different teams or projects.
- Dynamically generating views based on user input or external triggers.
- Integrating with other workflows that require specific data presentations from Bitable tables.
For example, a project management workflow could automatically create a view filtered by task status whenever a new project is initiated.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: Tenant Token, OAuth2 |
| App Token | The unique token identifying the Bitable app where the view will be created |
| Table Id | Identifier of the table within the Bitable app where the new view will be added |
| View Name | The name assigned to the new view |
| View Type | The type/category of the view being created (e.g., grid, gallery, calendar) |
| Custom Body | JSON object allowing full customization of the request body sent to create the view |
| Options > Use Custom Body | Boolean flag indicating whether to send the custom JSON body instead of standard parameters |
Output
The node outputs JSON data representing the newly created view object returned by the Lark Suite API. This typically includes details such as the view's ID, name, type, and any metadata associated with it.
If binary data were involved (not indicated here), it would represent files or attachments related to the view, but this node focuses on JSON responses only.
Dependencies
- Requires an active connection to Lark Suite's Open APIs.
- Needs either a Tenant Token or OAuth2 authentication credential configured in n8n.
- The base URL for API requests is
https://open.larksuite.com/open-apis. - The node depends on the presence of a valid Bitable app token and table ID to identify where the view should be created.
Troubleshooting
- Invalid App Token or Table ID: Ensure these identifiers are correct and correspond to existing resources in your Lark Suite environment.
- Authentication Errors: Verify that the selected authentication method is properly configured and authorized.
- API Rate Limits or Permissions: The API may reject requests if rate limits are exceeded or if the authenticated user lacks permissions to create views.
- Malformed Custom Body: If using the custom JSON body option, ensure the JSON is well-formed and matches the expected schema for creating views.
Common error messages might include unauthorized access, resource not found, or validation errors on input fields. Checking credentials, tokens, and input formats usually resolves these issues.