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 enables sending messages through the Lark messaging platform. It is designed to facilitate communication by programmatically delivering messages to users or chats identified by various ID types. This node is useful in automation workflows where notifications, alerts, or updates need to be sent automatically to team members or chat groups within Lark.
Common scenarios include:
- Sending automated status updates to a project chat.
- Delivering alerts or reminders to specific users based on their user IDs or emails.
- Broadcasting announcements to multiple recipients using different identification methods.
For example, you can configure this node to send a text message to a user identified by their email address or to a chat group using its chat ID.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests: either using a Tenant Token or OAuth2 authentication. |
| Receive Id Type | The type of identifier used for the message recipient. Options: open_id, user_id, union_id, email, or chat_id. |
| Content | The textual content of the message to be sent. |
| Msg Type | The type of the message (e.g., text, image, etc.). |
| Receive Id | The identifier of the message recipient, corresponding to the selected Receive Id Type. |
| Custom Body | A JSON object allowing the user to specify a custom request body for the message, overriding standard fields. |
| Options > Use Custom Body | Boolean flag indicating whether to use the Custom Body instead of the standard message properties. |
Output
The node outputs JSON data representing the response from the Lark messaging API after attempting to send the message. This typically includes information about the success or failure of the operation and any relevant metadata returned by the API.
If binary data were involved (e.g., sending images), it would be summarized here, but this node focuses on JSON message content.
Dependencies
- Requires an active connection to the Lark Open API endpoint (
https://open.larksuite.com/open-apis). - Needs valid authentication credentials, either a Tenant Token or OAuth2 token, configured in n8n.
- No additional external dependencies beyond the Lark API and proper credential setup.
Troubleshooting
- Authentication errors: Ensure that the correct authentication method is selected and that the provided credentials are valid and have sufficient permissions.
- Invalid Receive Id or Receive Id Type: Verify that the recipient ID matches the specified ID type and exists in the Lark system.
- Message format errors: If using the standard properties, ensure that
contentandmsg_typeare correctly set. When using a custom body, validate the JSON structure to match the API requirements. - API rate limits or network issues: Check network connectivity and API usage quotas if messages fail intermittently.