Overview
This node constructs LINE messaging API message objects of various types, including text, image, video, audio, location, flex messages, and stickers. It is useful for automating the creation of LINE messages within workflows, enabling users to send rich content through LINE channels programmatically.
Specifically, when using the "Sticker" operation, the node creates a sticker message object that can be sent via the LINE Messaging API. This is beneficial in scenarios where you want to send predefined stickers as part of automated chat responses or notifications.
Example use cases:
- Sending a specific sticker in response to a user query.
- Automating sticker replies in chatbots.
- Including stickers in broadcast messages to enhance engagement.
Properties
| Name | Meaning |
|---|---|
| Package ID | The identifier for a set of stickers. This corresponds to the sticker package available on LINE. For valid package IDs, refer to the official LINE sticker list documentation: https://developers.line.biz/en/docs/messaging-api/sticker-list/ |
| Sticker ID | The identifier for a specific sticker within the package. Valid sticker IDs are listed in the same LINE documentation linked above. |
| Quote Token | (Optional) A token representing the message to quote. This allows the sticker message to quote a previous message in a conversation. |
Output
The node outputs an array of JSON objects, each containing a message field structured according to the LINE Messaging API message format.
For the "Sticker" operation, the output JSON structure looks like this:
{
"message": {
"type": "sticker",
"packageId": "string",
"stickerId": "string",
"quoteToken": "string (optional)"
}
}
type: Always"sticker"for this operation.packageId: The sticker package identifier.stickerId: The specific sticker identifier.quoteToken: Optional; if provided, the sticker message will quote another message.
No binary data output is produced by this node.
Dependencies
- Requires access to the LINE Messaging API to send the constructed message objects.
- Users must provide valid package and sticker IDs as per LINE's official sticker list.
- No internal credentials are specified here, but sending messages typically requires an API authentication token configured elsewhere in n8n.
Troubleshooting
- Invalid Package ID or Sticker ID: If the provided IDs do not match those supported by LINE, the message may fail to send. Verify IDs against the official LINE sticker list.
- Missing Required Properties: Both
Package IDandSticker IDare required. Omitting them will cause errors. - Quote Token Issues: Providing an invalid or expired quote token might cause the message quoting to fail.
- API Errors: Since this node only constructs the message object, ensure that downstream nodes or integrations correctly handle authentication and API calls to LINE.
Links and References
- LINE Messaging API Sticker List: https://developers.line.biz/en/docs/messaging-api/sticker-list/