Overview
This node constructs message objects for the LINE messaging platform, supporting multiple message types such as text, image, video, audio, location, flex messages, and stickers. It is useful when you want to programmatically create LINE-compatible messages within an n8n workflow, for example, to automate sending notifications, media content, or interactive messages via LINE.
For the "Image" operation specifically, the node creates an image message object containing URLs for the original image and a preview image. This is beneficial when you want to send images with a preview thumbnail in LINE chats.
Properties
| Name | Meaning |
|---|---|
| URL | The URL of the original image file to be sent (required). Max length: 2000 characters. |
| Preview Url | The URL of the preview image shown as a thumbnail (required). Max length: 2000 characters. |
These properties are used to specify the image content for the message.
Output
The node outputs an array of JSON objects, each containing a message field structured according to the selected operation. For the "Image" operation, the output JSON structure is:
{
"message": {
"type": "image",
"originalContentUrl": "string", // URL of the full-size image
"previewImageUrl": "string" // URL of the preview thumbnail image
}
}
This output can be directly used by subsequent nodes that send messages through the LINE API or other integrations expecting this format.
Dependencies
- No external services or API keys are required by this node itself; it only formats message data.
- To actually send messages via LINE, you would need to connect this node's output to a node configured with appropriate LINE API credentials or webhook integration.
Troubleshooting
- Missing Required URLs: If either the original content URL or preview URL is missing or invalid, the constructed message will be incomplete and may cause errors downstream.
- Invalid JSON in Flex Messages: Although not relevant for the Image operation, if using the flex message type, ensure the JSON string provided is valid to avoid parsing errors.
- Incorrect Operation Selection: Selecting an operation but not providing its required parameters will result in incomplete message objects.