Actions5
Overview
The node "Lark Apps" provides management capabilities for Lark applications, specifically allowing users to update the category information of an app. This operation is useful when you want to modify or organize your app's classification within the Lark ecosystem, which can help in better categorization and discovery.
A practical example would be updating the categories of a productivity app to reflect new features or target audiences, ensuring it appears correctly in relevant sections of the Lark app store or management console.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" or "OAuth2". |
| Lang | Language code specifying the language of returned results (optional). |
| App Id | The unique identifier of the app whose category information is being updated (required). |
| Common Categories | A list of common category strings to assign to the app. Multiple categories can be added. |
| Custom Body | A JSON object allowing the user to specify a fully custom request body instead of using fields. |
| Use Custom Body | Boolean flag indicating whether to send the custom JSON body instead of the standard fields. |
Output
The node outputs JSON data representing the response from the Lark API after attempting to update the app's category information. This typically includes confirmation of success or details about any errors encountered.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication, either via a Tenant Token or OAuth2.
- Connects to the Lark Open API endpoint at
https://open.larksuite.com/open-apis. - Proper configuration of credentials in n8n is necessary for successful API calls.
Troubleshooting
- Authentication Errors: Ensure that the correct authentication method is selected and that the provided token or OAuth2 credentials are valid and have sufficient permissions.
- Invalid App ID: Verify that the App Id is correct and corresponds to an existing app in your Lark environment.
- Incorrect Category Format: When not using a custom body, ensure that categories are provided as an array of strings under "Common Categories".
- Custom Body Usage: If "Use Custom Body" is enabled, the JSON must be well-formed and match the expected API schema; otherwise, the request may fail.
- API Rate Limits: Be aware of potential rate limits imposed by the Lark API which could cause temporary failures.
Links and References
- Lark Open Platform Documentation
- Lark Apps Management API Reference (for detailed API specs)