Actions21
- App Actions
- Table Actions
- View Actions
- Record Actions
- Field Actions
Overview
The node provides access to records within a "bitable" app on the Lark Suite platform. Specifically, the "Get Records" operation retrieves data from a specified record in a table of a bitable app. This is useful for workflows that need to fetch and process specific data entries stored in Lark's collaborative database tables.
Common scenarios include:
- Automating data retrieval from Lark bitable apps for reporting or integration with other systems.
- Triggering downstream processes based on the content of specific records.
- Synchronizing data between Lark bitable and external databases or services.
Example: A user wants to fetch details of a customer order stored as a record in a bitable table and then use that data to generate an invoice or update another system.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: Tenant Token, OAuth2 |
| App Token | The unique identifier (app_token) of the bitable app from which to retrieve records |
| Table Id | Identifier of the specific table within the bitable app |
| Record Id | Identifier of the specific record within the table to retrieve |
| Options | Additional options for the request |
| - Use Custom Body | Boolean flag indicating whether to send a custom request body instead of the default |
Output
The node outputs JSON data representing the retrieved record from the specified table in the bitable app. The structure typically includes fields corresponding to the record's columns and their values.
If binary data were supported, it would represent file attachments or media linked to the record, but this operation focuses on JSON record data only.
Dependencies
- Requires authentication via either a Tenant Token or OAuth2 credentials for Lark Suite API access.
- Needs valid identifiers for the bitable app (
app_token), table (table_id), and record (record_id). - The node communicates with the Lark Suite Open APIs at
https://open.larksuite.com/open-apis.
Troubleshooting
- Invalid App Token, Table Id, or Record Id: Ensure these IDs are correct and correspond to existing resources in your Lark bitable app.
- Authentication Errors: Verify that the provided authentication method and credentials are valid and have sufficient permissions.
- Network or API Errors: Check connectivity and API rate limits; ensure the base URL is accessible.
- Use Custom Body Option: If enabled incorrectly, the request may fail due to malformed payloads.
Common error messages might include unauthorized access, resource not found, or invalid parameter errors. Resolving them usually involves verifying credentials, IDs, and request formatting.