Overview
This node is designed to create and send various types of messages compatible with the Line messaging platform. It supports multiple message formats such as text, image, video, audio, location, flex messages, and stickers. The node is useful in automation workflows where sending customized Line messages based on dynamic input data is required. For example, it can be used to notify users with a text update, share images or videos, send location details, or deliver rich interactive content using flex messages.
Properties
| Name | Meaning |
|---|---|
| Text | The text message you want to send to the user. |
(Note: The above table reflects the "Text" operation properties only, as requested.)
Output
The output of this node is an array of objects, each containing a json field with a message object inside. The structure of the message object depends on the selected operation:
For the text operation, the message object has:
{ "type": "text", "text": "Your text message here" }Other supported message types (not detailed here) include:
- Image: contains URLs for original and preview images.
- Video: contains URLs for original and preview videos.
- Audio: contains URL and duration.
- Location: includes title, address, latitude, and longitude.
- Flex: includes alternative text and parsed JSON content.
- Sticker: includes package ID, sticker ID, and optional quote token.
The node does not output binary data; all outputs are JSON objects representing the message payloads.
Dependencies
- This node requires no external libraries beyond what is bundled.
- To actually send messages via Line, appropriate API credentials and configurations must be set up elsewhere in the workflow or environment (not handled directly by this node).
- The node expects valid URLs and properly formatted JSON strings for certain message types (e.g., flex content).
Troubleshooting
- Invalid JSON in Flex Content: If the flex message content is not valid JSON, parsing will fail. Ensure the flexContent property contains correctly formatted JSON.
- Missing Required Parameters: Each message type requires specific parameters (e.g., text for text messages, URLs for images/videos). Omitting these may cause errors or invalid messages.
- Incorrect URLs: For media messages, ensure that the URLs provided are accessible and correctly formatted.
- Unsupported Operation: If an unsupported operation is specified, the node will not generate a message object, resulting in empty or missing output.