Actions4
Overview
This node integrates with the Line Messaging API to send replies to messages using a reply token. It is designed to respond directly to incoming messages in a conversation, making it useful for chatbots or automated messaging systems that need to acknowledge or continue conversations contextually.
Typical use cases include:
- Replying to user messages in a chatbot flow.
- Sending contextual responses based on user input.
- Quoting previous messages in replies.
- Adding quick reply buttons to facilitate user interaction.
For example, when a user sends a message, this node can reply with a text message and optionally include quick reply options for the user to choose from, enhancing interactivity.
Properties
| Name | Meaning |
|---|---|
| Reply Token | The token used to reply to a specific message. If not provided, the message will be sent as a new message instead of a reply. |
| Messages | A collection of messages to send as a reply. Each message supports: |
| - Type | The type of message. Currently only "Text Message (V2)" is supported. |
| - Quote Token | A token to quote a specific message in the reply. If omitted, the message is sent without quoting. |
| - Text | The text content of the message to send. |
| - Quick Reply | Optional quick reply items to add interactive buttons to the message. Each quick reply item includes: |
| -- Label | The label shown on the quick reply button. |
| -- Action Type | The action triggered by the quick reply button. Options are "Postback" (sending data back to the bot) or "Message" (sending a predefined message). |
| -- Data | The data payload sent when the quick reply button is pressed. The format depends on the selected action type. |
Output
The node outputs an array of JSON objects representing the response from the Line Messaging API after sending the reply. This typically includes status information about the sent messages.
If binary data were involved (not in this case), it would represent media content such as images or files sent via the API.
Dependencies
- Requires an API key credential for authenticating with the Line Messaging API.
- The node must be configured with valid credentials to interact with the Line Messaging service.
- Network access to the Line Messaging API endpoints is necessary.
Troubleshooting
- Missing or invalid reply token: The node requires a valid reply token to send a reply. If missing or expired, the API call will fail. Ensure the token is correctly obtained from the incoming message event.
- Invalid message format: Providing unsupported message types or malformed quick reply data may cause errors. Validate message structure before sending.
- Authentication errors: Incorrect or missing API credentials will prevent the node from communicating with the Line API. Verify credentials are set up properly.
- API rate limits: Excessive messaging may trigger rate limiting by the Line API. Implement retry logic or reduce message frequency if encountering rate limit errors.