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 perform various operations related to LINE's Rich Menu feature. Specifically, for the "Link Rich Menu to User" operation, it associates a specified rich menu with a particular user ID. This allows the user to see and interact with the linked rich menu in their LINE chat interface.

This node is beneficial when you want to dynamically assign or change the rich menu displayed to users based on certain triggers or workflows within n8n. For example, after a user completes a registration process, you might link a custom rich menu tailored to their profile or preferences.

Properties

Name Meaning
Rich Menu ID The identifier of the rich menu to link to the user.

Note: Although not listed in the provided properties JSON, the operation also requires a User ID parameter (as seen in the source code) which specifies the target user to whom the rich menu will be linked.

Output

The output is a JSON object representing the response from the LINE Messaging API after attempting to link the rich menu to the user. This typically includes confirmation of success or details about any errors encountered.

No binary data output is involved in this operation.

Example output structure (conceptual):

{
  "message": "Rich menu linked successfully",
  "userId": "Uxxxxxxxxxxxxxx",
  "richMenuId": "richmenu-xxxxxxxx"
}

Dependencies

  • Requires an API key credential for authentication with the external service managing the LINE Messaging API requests.
  • The node optionally validates the subscription and API key against an external validation endpoint before executing the main operation.
  • The node depends on the bundled line-api module for interacting with the LINE Messaging API.
  • Proper configuration of credentials and permissions to access the LINE Messaging API is necessary.

Troubleshooting

  • Invalid API Key or Subscription: If the node throws an error indicating invalid subscription or API key, verify that the API key credential is correctly configured and active.
  • Missing User ID or Rich Menu ID: Ensure both the user ID and rich menu ID are provided; missing these will cause the operation to fail.
  • Permission Issues: The LINE Messaging API may reject requests if the authenticated account lacks permission to link rich menus to users.
  • Network or Endpoint Errors: Connectivity issues or incorrect API URLs can cause failures; check network settings and credential configurations.
  • Error Messages: The node surfaces errors returned by the LINE API or the validation endpoint. Reading the error message carefully usually indicates the cause and how to fix it.

Links and References

Discussion