Line Webhook icon

Line Webhook

Handle incoming events from LINE Messaging API
Join our community

Overview

This node acts as a webhook trigger for the LINE Messaging API, allowing workflows to respond to various LINE events such as messages, postbacks, follows, joins, and more. It is useful for automating responses or processing data based on user interactions within the LINE platform. For example, it can trigger workflows when a user sends a text message, shares their location, or interacts with a postback button.

Use Case Examples

  1. Trigger a workflow when a user sends a text message to a LINE bot to provide automated customer support.
  2. Start a workflow when a user joins a LINE group to send a welcome message.
  3. Process location events to provide location-based services or promotions.

Properties

Name Meaning
Path The URL path for the webhook endpoint that LINE will send events to. This is required to set up the webhook URL in LINE's developer console.
Trigger On Specifies which LINE event types will trigger the workflow. Users can select one or multiple event types or choose all events with '*'.

Output

JSON

  • eventType - The type of LINE event received (e.g., message, postback, follow).
  • timestamp - The timestamp when the event occurred.
  • source - Information about the source of the event (user, group, or room).
  • rawEvent - The full raw event object received from LINE.
  • replyToken - Token used to reply to the event (present for certain event types).
  • message - The message object for message events.
  • postback - The postback data for postback events.
  • beacon - The beacon data for beacon events.
  • link - The account link data for account link events.

Dependencies

  • LINE Messaging API SDK

Troubleshooting

  • Ensure the webhook URL path matches the 'Path' property and is correctly configured in the LINE developer console.
  • Verify that the LINE Messaging API credentials (channel secret and access token) are correctly set up and valid.
  • If events are not triggering, check that the selected event types in 'Trigger On' include the events being sent by LINE.
  • Common error: 'Webhook processing failed' indicates issues with event validation or credential misconfiguration. Check logs for detailed error messages.

Links

Discussion