Overview
This node acts as a trigger for workflows based on events received from the Line Messaging platform. It listens to incoming webhook events and starts the workflow when specified types of Line Messaging events occur. This is useful for automating responses or processing data whenever certain user interactions happen on Line, such as receiving messages, users joining or leaving groups, postbacks, and more.
Practical examples include:
- Automatically responding to user messages.
- Tracking when users follow or unfollow a Line account.
- Handling postback actions triggered by buttons in Line chat.
- Monitoring membership changes in group chats.
Properties
| Name | Meaning |
|---|---|
| Trigger On | Select which Line Messaging event types should trigger the workflow. Options include: All, Message, Unsend, Follow, Unfollow, Join, Leave, MemberJoined, MemberLeft, Postback, VideoPlayComplete, Beacon, AccountLink, Membership |
Output
The node outputs an array of event objects under the json field. Each object corresponds to a Line Messaging event that matched the selected trigger criteria. The structure of each event object follows the Line Messaging API's event format, containing details such as event type, source, timestamp, and event-specific data.
No binary data output is produced by this node.
Dependencies
- Requires a valid API authentication credential for the Line Messaging platform (an API key or token).
- Needs the channel secret from the Line Messaging API credentials to verify incoming webhook signatures.
- The node expects to be configured with a webhook URL accessible by the Line platform to receive events.
Troubleshooting
- Invalid signature error (HTTP 403): This occurs if the incoming webhook request's signature does not match the expected signature computed using the channel secret. Ensure the correct channel secret is configured in the credentials and that the webhook URL is correctly set up in the Line developer console.
- No events triggered: Verify that the "Trigger On" property includes the event types you expect to handle. If "All" is not selected, only events matching the selected types will start the workflow.
- Webhook not receiving events: Confirm that the webhook URL is publicly accessible and properly registered in the Line Messaging API settings.