Lark Base icon

Lark Base

Lark Base Management

Actions21

Overview

The node interacts with the "View" resource of a Bitable app in Lark Suite, specifically supporting the "List View" operation. It retrieves a list of views associated with a specified table within a Bitable application. This is useful for workflows that need to dynamically access or manipulate views in a Bitable database, such as generating reports, syncing data, or automating view-based operations.

Practical examples include:

  • Automatically fetching all views of a table to display or process them downstream.
  • Integrating Bitable views into other systems by listing and selecting views programmatically.
  • Using the list of views to trigger further actions based on view properties.

Properties

Name Meaning
Authentication Method of authenticating API requests. Options: Tenant Token, OAuth2
App Token The unique token identifying the Bitable app. Can be selected from a list or entered manually as an ID.
Table Id The identifier of the table within the Bitable app whose views are to be listed.
Options Additional options for the request. Currently supports: Use Custom Body (boolean)

Output

The node outputs JSON data representing the list of views retrieved from the specified table in the Bitable app. Each item in the output corresponds to a view object containing details such as view ID, name, type, and other metadata provided by the Lark Suite API.

If binary data were involved (not indicated here), it would typically represent attachments or files related to views, but this node focuses on JSON data only.

Dependencies

  • Requires authentication via either a Tenant Token or OAuth2 credentials for Lark Suite API access.
  • Needs a valid Bitable app token and table ID to identify the target data.
  • The base URL for API requests is https://open.larksuite.com/open-apis.
  • No additional external dependencies beyond standard HTTP requests to Lark Suite APIs.

Troubleshooting

  • Invalid App Token or Table ID: Ensure the app token and table ID are correct and correspond to existing resources in your Bitable app.
  • Authentication Errors: Verify that the chosen authentication method is properly configured and the credentials are valid.
  • API Rate Limits or Permissions: The user or token may lack permissions to list views; check API scopes and roles.
  • Use Custom Body Option: If enabled incorrectly, it might cause malformed requests; use only if you know the required body structure.

Common error messages might include unauthorized access, resource not found, or invalid parameters. Resolving these usually involves checking credentials, tokens, and input IDs.

Links and References

Discussion