Actions5
- Image Recognition Actions
- Speech Recognition Actions
- Text Actions
Overview
The node provides integration with Lark AI services, specifically supporting text language recognition under the "Text" resource and "Text Language Recognition" operation. It allows users to send a piece of text to the Lark AI API to detect the language of the input text automatically.
This node is beneficial in scenarios where you need to identify the language of user-generated content, documents, or messages before further processing such as translation, sentiment analysis, or routing to language-specific workflows. For example, an application receiving multilingual customer feedback can use this node to detect the language and then trigger appropriate language-specific responses or analytics.
Properties
Name | Meaning |
---|---|
Authentication | Method of authenticating with the Lark AI API. Options: Tenant Token, OAuth2 |
Text | The text string whose language needs to be recognized |
Custom Body | A JSON object allowing the user to specify a custom request body instead of the default one |
Use Custom Body | Boolean flag indicating whether to use the custom JSON body for the request |
Output
The node outputs JSON data containing the results of the language recognition performed by the Lark AI API. The exact structure depends on the API response but typically includes detected language codes and confidence scores.
If binary data were supported (not indicated here), it would represent any associated files or media returned by the API, but this node focuses on JSON textual output only.
Dependencies
- Requires access to the Lark AI API endpoint at
https://open.larksuite.com/open-apis
. - Requires authentication via either a Tenant Token or OAuth2 credentials configured in n8n.
- No additional external dependencies are indicated beyond standard HTTP requests to the Lark AI service.
Troubleshooting
- Authentication errors: Ensure that the correct authentication method is selected and valid credentials are provided. Expired or invalid tokens will cause failures.
- Invalid input text: Sending empty or malformed text may result in API errors or no meaningful detection.
- Custom Body usage: If using the custom body option, ensure the JSON structure matches the API expectations; otherwise, the request may fail.
- API rate limits or connectivity issues: Network problems or exceeding API quotas can cause errors; verify network access and API usage limits.
Links and References
- Lark Open Platform Documentation
- Language Detection API Reference (specific to language recognition)