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
This node interacts with the Lark Messenger service to obtain the content of a specific message by its ID. It is useful in scenarios where you need to retrieve detailed information or the body of a particular message within Lark Messenger, such as for archiving, processing, or displaying message content in workflows.
For example, you might use this node to:
- Fetch the text or attachments of a message when triggered by an event.
- Integrate message content into other systems like CRM or databases.
- Automate responses or analysis based on message content.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to access Lark Messenger API. Options: Tenant Token, OAuth2. |
| Message Id | The unique identifier of the message whose content you want to obtain. |
| Options | Additional optional settings: |
| - Use Custom Body | Whether to send a custom request body instead of the default one (true/false). |
Output
The node outputs JSON data containing the content of the specified message. This typically includes fields such as the message text, sender information, timestamps, and any attachments or metadata associated with the message.
If the message contains binary data (e.g., images or files), the node may also output binary data representing those attachments.
Dependencies
- Requires valid authentication credentials for Lark Messenger API access, either via a tenant token or OAuth2.
- Needs network access to the Lark Suite open API endpoint (
https://open.larksuite.com/open-apis). - Proper configuration of authentication credentials in n8n is necessary before using this node.
Troubleshooting
- Invalid Message Id: If the provided message ID does not exist or is malformed, the node will likely return an error indicating the message was not found. Verify the message ID is correct.
- Authentication Errors: Using incorrect or expired credentials will cause authentication failures. Ensure that the tenant token or OAuth2 credentials are valid and have sufficient permissions.
- API Rate Limits: Frequent requests may hit rate limits imposed by Lark Suite APIs. Implement retry logic or reduce request frequency if encountering rate limit errors.
- Use Custom Body Option: Enabling "Use Custom Body" without providing a proper body structure may cause request failures. Only enable this if you know the exact request format required.