Actions38
- Message Actions
- Message Buzz Message Actions
- Message Batch Message Actions
- Message Image Actions
- Message File Actions
- Message Message Card Actions
- Message Message Reaction Actions
- Group Actions
- Group Group Member Actions
- Group Group Announcement Actions
Overview
The "Lark Messenger" node provides integration with the Lark messaging platform, enabling users to manage and interact with Lark Messenger services within n8n workflows. It supports authentication via either a tenant token or OAuth2, allowing flexible access depending on the user's setup.
Common scenarios for this node include sending messages, managing chats, or automating communication tasks in Lark Messenger as part of broader automation workflows. For example, it can be used to send notifications to team members when certain events occur or to automate message dispatch based on external triggers.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: Tenant Token, OAuth2 |
| Options | Additional optional settings: |
| - Use Custom Body | Boolean flag indicating whether to use a custom request body instead of default structure |
Output
The node outputs data in JSON format representing the response from the Lark Messenger API calls. This typically includes information about sent messages, chat details, or other relevant entities depending on the operation performed.
If binary data is involved (not indicated explicitly here), it would represent attachments or media related to messages, but this is not detailed in the provided code.
Dependencies
- Requires valid credentials for Lark Messenger API access, either via a tenant token or OAuth2.
- The node communicates with the Lark Suite open API endpoint at
https://open.larksuite.com/open-apis. - Proper configuration of these credentials in n8n is necessary for successful operation.
Troubleshooting
- Authentication errors: Ensure that the correct authentication method is selected and that the corresponding credentials are valid and have sufficient permissions.
- API request failures: Check network connectivity and verify that the Lark API service is operational.
- Invalid custom body usage: If "Use Custom Body" is enabled, ensure the custom body is correctly formatted according to Lark API specifications to avoid request errors.
- Missing or incorrect properties: Verify that all required input properties are set appropriately before execution.