Line Message Builder icon

Line Message Builder

Builds a message object for the LINE Messaging API.
Join our community

Actions8

Overview

This node builds message objects for the LINE Messaging API, supporting various message types such as text, image, video, audio, location, sticker, and flex messages. It is useful for automating the creation of LINE messages in workflows, enabling users to send customized messages including text with substitutions, media content, location data, stickers, and rich flex messages.

Use Case Examples

  1. Sending a simple text message to a LINE user.
  2. Creating a text message with user mentions or emojis using substitution keys.
  3. Sending an image or video message with preview URLs.
  4. Sharing a location with title, address, latitude, and longitude information in a message.

Properties

Name Meaning
Text The text content of the message, used in text and textV2 operations.

Output

JSON

  • message
    • type - The type of the LINE message (e.g., text, image, video, audio, location, sticker, flex).
    • text - The text content of the message (for text and textV2 types).
    • substitution - Substitution object for textV2 messages containing keys for mentions or emojis.
    • originalContentUrl - URL of the original content for image, video, or audio messages.
    • previewImageUrl - URL of the preview image for image or video messages.
    • duration - Duration of the audio message in milliseconds.
    • trackingId - Tracking ID for video play completion statistics.
    • title - Title for location messages.
    • address - Address for location messages.
    • latitude - Latitude coordinate for location messages.
    • longitude - Longitude coordinate for location messages.
    • packageId - Package ID for sticker messages.
    • stickerId - Sticker ID for sticker messages.
    • altText - Alternative text for flex messages.
    • contents - JSON object representing the contents of a flex message.

Dependencies

  • Requires an API key credential for LINE Messaging API to send the constructed messages.

Troubleshooting

  • If the 'Flex message contents' JSON is invalid, the node throws an error indicating the JSON is not valid. Ensure the JSON structure is correct before inputting.
  • For textV2 substitution, missing or incorrect keys or user IDs may cause the message to not render substitutions properly.
  • URLs for media content must be HTTPS and valid; otherwise, the message may fail to send or display.
  • Sticker packageId and stickerId must correspond to valid LINE stickers; invalid IDs will cause errors.

Links

Discussion