N8N Tools LINE icon

N8N Tools LINE

Interact with LINE Messaging API
Join our community

Actions16

Overview

The node integrates with the LINE Messaging API to send various types of messages and perform related messaging operations. Specifically, for the Messages - Reply Message operation, it sends a reply message in response to an incoming webhook event using a reply token. This is useful when you want to automatically respond to user messages or events on LINE, such as confirming receipt, providing information, or continuing a conversation.

Practical examples include:

  • Sending a text reply to a user who just sent a message.
  • Replying with images, videos, or stickers based on user input.
  • Automatically acknowledging commands or requests received via LINE chat.

Properties

Name Meaning
Message Type The type of message to send. Options: Text, Image, Video, Audio, File, Location, Sticker.
Message Text The actual text content of the message to send (used when Message Type is "Text").
Reply Token The reply token received from the webhook event, used to identify which message to reply to.

Output

The node outputs JSON data representing the response from the LINE Messaging API after sending the reply message. This typically includes status information about the message delivery.

If the message involves binary content (e.g., image, video), the node handles sending it but does not output binary data itself; the output remains JSON metadata about the operation result.

Dependencies

  • Requires an API key credential for authenticating with the LINE Messaging API.
  • Optionally uses an external validation service ("N8N Tools API") to verify subscription and API key validity before executing the main request.
  • The node depends on the bundled LineApi class that abstracts the LINE Messaging API calls.

Troubleshooting

  • Invalid subscription or API key error: If the external validation fails with 401 or 403 status, check that your API key credential is correct and active.
  • Missing or invalid reply token: Ensure the reply token is correctly obtained from the webhook event and passed to the node.
  • Unsupported message type: Only the listed message types are supported; using unsupported types will cause errors.
  • Network or API errors: Check connectivity and LINE API status if requests fail unexpectedly.
  • Enable "Continue On Fail" in the node settings to handle errors gracefully without stopping workflow execution.

Links and References

Discussion