Lark Apps

Lark Apps Management

Actions5

Application Actions

Overview

This node manages Lark Apps, specifically allowing users to update version information of an application within the Lark platform. It is useful for developers or administrators who need to programmatically modify app version details such as status or other metadata. For example, you might use this node to mark a specific app version as active, deprecated, or under review by updating its status field.

Properties

Name	Meaning
Authentication	Method of authentication to use: either "Tenant Token" or "OAuth2".
User Id Type	Category of user ID provided; options include `open_id`, `union_id`, or `user_id`. Optional.
Operator Id	The operator's open_id (identifier of the user performing the update). Optional.
App Id	The unique identifier of the app whose version info is being updated. Required.
Version Id	The unique identifier of the app version to update. Required.
Status	Numeric status value to set for the app version (e.g., 0).
Custom Body	JSON object to send as a custom request body instead of the standard fields.
Options > Use Custom Body	Boolean flag indicating whether to send the custom JSON body instead of the standard one.

Output

The node outputs JSON data representing the response from the Lark API after attempting to update the app version information. This typically includes confirmation of the update, any returned metadata about the app version, or error messages if the update failed. There is no indication that binary data is output.

Dependencies

Requires access to the Lark Open API at https://open.larksuite.com/open-apis.
Requires authentication via either a Tenant Token or OAuth2 credentials.
Proper configuration of these credentials in n8n is necessary for successful API calls.

Troubleshooting

Common issues:
- Invalid or missing app_id or version_id will cause the update to fail.
- Incorrect authentication setup may result in authorization errors.
- Using an invalid status value could lead to API rejection.
- If using a custom body, malformed JSON or missing required fields can cause errors.
Error messages and resolutions:
- Unauthorized / 401: Check that the API key or OAuth token is valid and has sufficient permissions.
- Not Found / 404: Verify that the app_id and version_id correspond to existing resources.
- Bad Request / 400: Ensure all required parameters are correctly formatted and included.
- Internal Server Error / 500: Retry later or contact Lark support if persistent.