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 "Send Buzz Text Messages" operation in the Lark Messenger node allows users to send a "buzz" notification to specific recipients for a given message. This feature is useful when you want to draw attention to an important message by sending a nudge or alert to selected users within the Lark messaging platform.
Common scenarios include:
- Alerting team members about urgent updates or announcements.
- Prompting users to review or respond to a particular message.
- Enhancing communication by ensuring key messages are noticed promptly.
For example, after posting a critical project update, you can use this node to buzz all relevant stakeholders so they receive a direct notification.
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 notification 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 the standard parameters. |
| Options → Use Custom Body | Boolean flag to indicate whether to use the Custom Body property instead of the standard input fields. |
Output
The node outputs JSON data representing the response from the Lark API after attempting to send the buzz notifications. This typically includes status information indicating success or failure and any relevant metadata returned by the API.
If the node supports binary data output, it is not applicable here as the operation deals with sending notifications and does not produce binary content.
Dependencies
- Requires valid authentication credentials for the Lark platform, either via a Tenant Token or OAuth2.
- Needs network access to the Lark Open API endpoint at
https://open.larksuite.com/open-apis. - Proper configuration of credentials in n8n is necessary to authorize API calls.
Troubleshooting
- Invalid or missing Message Id: The operation requires a valid message ID. Ensure the message ID is correct and corresponds to an existing message.
- Incorrect User Id Type: If user IDs do not match the specified user ID type (
open_id,union_id, oruser_id), the API may reject the request. - Authentication errors: Verify that the chosen authentication method is correctly configured and the credentials are valid.
- Empty User Id List: Sending a buzz without specifying any recipients will likely fail; ensure at least one user ID is provided.
- Custom Body format issues: When using the custom body option, ensure the JSON structure matches the API requirements exactly to avoid request errors.