Overview
This node sends messages to a Lark webhook URL using different message formats. It supports sending plain text, markdown, post (rich text with multiple elements), and card (interactive UI cards) messages. This node is useful for automating notifications or alerts in Lark chat groups or channels by pushing customized content programmatically.
Common scenarios include:
- Sending simple text alerts or status updates.
- Posting rich formatted messages with multiple sections or fields.
- Delivering interactive cards with buttons or other UI elements.
- Sharing markdown-formatted content for better readability.
Example: Automatically notify a team channel in Lark when a deployment finishes, using a card message with buttons linking to logs or dashboards.
Properties
| Name | Meaning |
|---|---|
| Send Type | The type of message to send. Options: Text, Post, Card, Markdown |
| Send Content | The textual content of the message to send. Used when Send Type is Text or Markdown |
| JSON Content | The JSON string representing the message content. Used when Send Type is Post or Card |
Output
The node outputs the original input data augmented with a response field inside the json property. This response contains:
status: HTTP status code returned by the Lark webhook API.headers: HTTP response headers.data: The response body from the Lark API.others: The raw JSON content sent for Post or Card message types (parsed from the input).
No binary data output is produced by this node.
Dependencies
- Requires an API key credential configured with the Lark webhook URL.
- Uses the Axios HTTP client library to send POST requests to the Lark webhook endpoint.
Troubleshooting
- Missing credentials error: If no webhook URL credential is provided, the node will throw an error. Ensure the Lark webhook API credential is properly set up.
- Invalid JSON content: For Post and Card message types, the JSON content must be valid JSON. Malformed JSON will cause parsing errors.
- HTTP errors: If the webhook URL is incorrect or the network is unreachable, the node will throw an error with details from the Axios request.
- Unsupported message type: Only the four specified message types are supported; others will not work.