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 messages and related actions. The Send Phone Call Buzz operation under the Message Buzz Message resource allows users to send a "buzz" notification via phone call to specified users for a particular message. This can be useful in scenarios where urgent attention is needed on a message, such as alerting team members about critical updates or reminders.

Practical examples include:

  • Notifying a group of users immediately about an important announcement by buzzing them on their phones.
  • Sending a buzz to specific users after posting a message that requires quick feedback or action.

Properties

Name Meaning
Authentication Method of authenticating API requests. Options: Tenant Token, OAuth2.
User Id Type Specifies the type/category of user IDs provided. Optional values: open_id, union_id, user_id.
Message Id The unique identifier of the message to which the buzz will be sent. (Required)
User Id List A list of user IDs to receive the buzz notification. Multiple user IDs can be added.
Custom Body Allows sending a fully custom JSON body instead of using predefined parameters.
Use Custom Body Boolean flag indicating whether to use the Custom Body JSON instead of standard parameters.

Output

The node outputs JSON data representing the response from the Lark API after attempting to send the phone call buzz. This typically includes status information about the request, such as success confirmation or error details.

If the node supports binary data output, it would represent any binary content returned by the API, but in this case, the operation deals with notifications and does not produce binary output.

Dependencies

  • Requires valid authentication credentials for Lark API access, either via a Tenant Token or OAuth2 token.
  • Needs network connectivity to https://open.larksuite.com/open-apis.
  • Proper configuration of authentication credentials within n8n is necessary.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication tokens leading to authorization errors.
    • Incorrect or missing message_id causing the API to reject the request.
    • Providing user IDs in an unsupported format or empty user ID list.
    • Using the custom body option incorrectly formatted JSON.

  • Error Messages:

    • Authorization errors: Check that the correct authentication method is selected and credentials are valid.
    • Validation errors: Ensure required fields like message_id and user_id_list are correctly populated.
    • API rate limits: If too many requests are made in a short time, wait and retry later.

Links and References

Discussion