Message → Multicast
AI-generatedOverview
This node interacts with the LINE Messaging API to send multicast messages to multiple users. It supports sending various types of messages including text, image, video, audio, location, sticker, and flex messages. Users can specify a comma-separated list of user IDs (up to 500) to receive the message. The node also supports adding quick reply buttons to messages, which can be configured either via a visual builder or JSON. This node is useful for scenarios where a message needs to be broadcasted to a specific group of users, such as marketing campaigns, notifications, or updates.
Use Case Examples
- Sending a text multicast message to multiple users to announce a new product.
- Sending an image multicast message with a preview to a group of users for promotional purposes.
- Sending a location multicast message to multiple users to share an event venue.
- Adding quick reply buttons to a multicast message to gather user feedback or responses.
Properties
| Name | Meaning |
|---|---|
| User IDs | Comma-separated list of user IDs to send the message to (max 500) |
| Message Type | The type of message to send (text, image, video, audio, location, sticker, flex) |
| Text | The text message to send (required if message type is text) |
| Original Content URL | URL of the original content for image, video, or audio messages (must be HTTPS) |
| Preview Image URL | URL of the preview image for image or video messages (must be HTTPS) |
| Title | The title of the location (required if message type is location) |
| Address | The address of the location (required if message type is location) |
| Latitude | The latitude of the location (required if message type is location) |
| Longitude | The longitude of the location (required if message type is location) |
| Package ID | The package ID of the sticker (required if message type is sticker) |
| Sticker ID | The sticker ID (required if message type is sticker) |
| Alt Text | Alternative text for devices that do not support flex messages (required if message type is flex) |
| Flex Contents | The flex message container in JSON format (required if message type is flex) |
| Add Quick Reply | Whether to add quick reply buttons to the message (max 13 items) |
| Quick Reply Mode | Choose how to configure quick reply buttons (builder or JSON) |
| Quick Reply JSON | Quick reply configuration in JSON format. Must contain an "items" array (used if Quick Reply Mode is JSON) |
| Quick Reply Items | Quick reply button items configured via visual builder (used if Quick Reply Mode is builder) |
Output
JSON
jsonmessageId- The message ID (for getContent operation)mimeType- The MIME type of the content (for getContent operation)size- The size of the content in bytes (for getContent operation)
binary- Binary data of the downloaded content (for getContent operation)
Dependencies
- LINE Messaging API
- an API key credential for authentication
Troubleshooting
- Ensure the user IDs list does not exceed 500 users to avoid API errors.
- Verify that URLs for original content and preview images use HTTPS as required by the API.
- If sending flex messages, ensure the JSON format of flexContents is valid to prevent parsing errors.
- When adding quick reply buttons, limit the number of items to 13 to comply with API constraints.
- Common error messages may include authentication failures, invalid user IDs, or malformed message payloads. Check API credentials and input data for correctness.
Links
- LINE Messaging API - Send multicast message - Official documentation for sending multicast messages using the LINE Messaging API.