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 node "Lark Messenger" provides management capabilities for Lark Messenger, a communication platform. Specifically, the "Recall Messages" operation allows users to recall (i.e., delete or retract) a previously sent message by specifying its message ID. This is useful in scenarios where a message was sent by mistake or contains errors and needs to be removed from the conversation.
Practical examples include:
- Automatically recalling messages that contain sensitive information sent in error.
- Building workflows that clean up messages after a certain time period.
- Allowing users to trigger message recalls via automation when specific conditions are met.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: "Tenant Token" or "OAuth2". |
| Message Id | The unique identifier of the message to be recalled. Required to specify which message to recall. |
| Options | Additional optional settings. Currently supports: "Use Custom Body" (boolean) to send a custom request body instead of the default. |
Output
The node outputs JSON data representing the response from the Lark Messenger API after attempting to recall the message. This typically includes status information indicating whether the recall was successful or if an error occurred.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Lark Suite Open APIs at
https://open.larksuite.com/open-apis. - Requires authentication credentials, either a Tenant Token or OAuth2 token, configured in n8n.
- The node sends HTTP requests with JSON payloads and expects JSON responses.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens will cause authorization failures.
- Providing an incorrect or non-existent message ID will result in errors indicating the message cannot be found or recalled.
- Network connectivity issues can prevent the API call from succeeding.
Error messages and resolutions:
- Unauthorized / 401 errors: Check that the API credentials are correctly set up and have not expired.
- Message not found / 404 errors: Verify the message ID is correct and that the message exists.
- Bad Request / 400 errors: If using the custom body option, ensure the JSON structure matches the API requirements.
- Timeouts or network errors: Confirm internet connectivity and that the Lark API endpoint is reachable.