Lark Messenger icon

Lark Messenger

Lark Messenger Management

Actions38

Overview

The node "Lark Messenger" provides integration with the Lark messaging platform, specifically enabling management of batch messages. The operation "Recall Messages In Batches" allows users to recall (i.e., retract or delete) a previously sent batch message by specifying its batch message ID.

This functionality is useful in scenarios where a batch message was sent in error or needs to be withdrawn from recipients. For example, an organization might send a batch announcement but later realize it contains incorrect information and want to recall it promptly.

Properties

Name Meaning
Authentication Method of authenticating API requests. Options: "Tenant Token" or "OAuth2".
Batch Message Id The unique identifier of the batch message that you want to recall.
Options Additional optional settings. Currently supports:
- Use Custom Body Boolean flag indicating whether to use a custom request body for the recall operation.

Output

The node outputs JSON data representing the response from the Lark API after attempting to recall the batch message. This typically includes success status and any relevant metadata about the recall operation.

No binary data output is indicated.

Dependencies

  • Requires access to the Lark Suite Open API endpoint at https://open.larksuite.com/open-apis.
  • Requires authentication via either:
    • A Tenant Token credential.
    • An OAuth2 credential.
  • Proper configuration of these credentials within n8n is necessary for successful API calls.

Troubleshooting

  • Invalid Batch Message Id: If the provided batch message ID does not exist or is malformed, the API will likely return an error. Verify the ID before retrying.
  • Authentication Errors: Using incorrect or expired credentials will cause authentication failures. Ensure the selected authentication method is correctly configured and valid.
  • Permission Issues: The authenticated user or token must have permission to recall batch messages. Lack of permissions will result in authorization errors.
  • Use Custom Body Misconfiguration: If "Use Custom Body" is enabled but the custom body is improperly formatted or missing required fields, the API call may fail. Double-check the custom payload structure.

Links and References

Discussion