Actions16
- Messages Actions
- Profile Actions
- Rich Menu Actions
- Webhook Actions
Overview
The node integrates with the LINE Messaging API to send various types of messages to users. Specifically, for the Messages - Push Message operation, it allows sending a message directly to a specified user by their User ID. This is useful in scenarios where you want to proactively notify or communicate with a user outside of a reply context, such as sending alerts, updates, or promotional content.
Practical examples include:
- Sending a text notification to a user when a new order is placed.
- Pushing an image or sticker as part of a marketing campaign.
- Delivering location information or files directly to a user.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the LINE user to whom the message will be sent. |
| Message Type | The type of message to send. Options: Text, Image, Video, Audio, File, Location, Sticker. |
| Message Text | The textual content of the message (used only if Message Type is "Text"). |
Output
The node outputs JSON data representing the response from the LINE Messaging API after attempting to push the message. This typically includes status information about the message delivery.
If an error occurs during execution and "Continue On Fail" is enabled, the output JSON will contain an error field with the error message.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authentication with the external service called "N8N Tools API" which acts as a validation layer before calling the LINE Messaging API.
- The node internally uses a helper class to interact with the LINE Messaging API endpoints.
- No additional environment variables are explicitly required beyond the configured credentials.
Troubleshooting
- Invalid subscription or API key error: If the node throws an error indicating invalid subscription or API key, verify that the API key credential is correctly set up and has the necessary permissions.
- Unknown operation error: This can occur if an unsupported operation name is provided. Ensure the operation parameter is set to "pushMessage" for this use case.
- Empty or incorrect User ID: Messages will fail if the User ID is missing or invalid. Double-check the User ID value.
- Message content issues: For non-text message types, additional properties might be required (not covered here). Sending a text message with empty content may result in errors.