Actions4
Overview
This node integrates with the Line Messaging API to send messages to multiple users simultaneously using the "Multicast" operation. It is useful when you want to broadcast a message or notification to a group of up to 500 recipients at once, such as sending announcements, alerts, or promotional content.
Practical examples include:
- Sending a company-wide update to all employees.
- Broadcasting event invitations to a list of customers.
- Delivering reminders or notifications to a selected user group.
Properties
| Name | Meaning |
|---|---|
| User IDs | Comma-separated list of User IDs to send the message to (maximum 500 recipients). |
| Messages | One or more messages to send. Each message can be: |
| Type | Currently supports "Text Message (V2)". |
| Quote Token | Optional token to quote a previous message; if omitted, sends as a new message. |
| Text | The text content of the message to send. |
| Quick Reply | Optional quick reply buttons attached to the message. Each quick reply item includes: |
| Label | Label shown on the quick reply button. |
| Action Type | Action triggered by the quick reply, either "Postback" or "Message". |
| Data | Data sent with the quick reply action, format depends on the action type. |
Output
The node outputs an array of JSON objects representing the response from the Line Messaging API multicast request. This typically includes status information about the message delivery.
If binary data were supported, it would represent media content or attachments, but this node focuses on text-based messaging and quick replies only.
Dependencies
- Requires an API key credential for authenticating with the Line Messaging API.
- The node must be configured with valid credentials that allow access to the Line Messaging service.
- Network connectivity to the Line Messaging API endpoints is necessary.
Troubleshooting
- Error: Invalid User IDs — Ensure the User IDs are correctly formatted and exist in the Line platform. The maximum number of recipients is 500.
- Error: Authentication Failed — Verify that the API key credential is valid and has not expired or been revoked.
- Error: Message Format Invalid — Check that the message structure matches the expected schema, especially for quick replies and quote tokens.
- Rate Limiting Errors — If sending too many requests in a short time, the API may throttle requests. Implement retries with backoff.
- Empty or Missing Messages — Make sure at least one message is provided in the "Messages" property.