N8N Tools LINE icon

N8N Tools LINE

Interact with LINE Messaging API
Join our community

Actions16

Overview

The node provides integration with the LINE Messaging API, specifically enabling management of Rich Menus within LINE. The "Create Rich Menu" operation allows users to create a new Rich Menu by specifying its name. Rich Menus are customizable menus that appear in LINE chat interfaces, providing interactive buttons and options for users.

This node is beneficial in scenarios where businesses or developers want to enhance user interaction on their LINE official accounts by creating custom menus that improve navigation and engagement. For example, a restaurant could create a Rich Menu with buttons for viewing the menu, making reservations, or contacting support directly from the chat interface.

Properties

Name Meaning
Rich Menu Name The name assigned to the new Rich Menu being created.

Output

The output JSON contains the response from the LINE Messaging API after attempting to create the Rich Menu. This typically includes details about the newly created Rich Menu such as its ID and configuration status.

No binary data output is produced by this operation.

Example output structure (simplified):

{
  "richMenuId": "string",
  "status": "success"
}

Dependencies

  • Requires an API key credential for authentication with the LINE Messaging API.
  • Optionally uses an additional API key credential for validation via an external service ("N8N Tools API") if configured.
  • The node depends on the bundled line-api module which handles communication with the LINE API endpoints.
  • No special environment variables are required beyond standard n8n credential setup.

Troubleshooting

  • Invalid subscription or API key error: If the node throws an error indicating invalid subscription or API key, verify that the provided API credentials are correct and have sufficient permissions to create Rich Menus.
  • Network or HTTP errors: Ensure that the n8n instance has internet access and can reach the LINE API endpoints.
  • Missing or empty Rich Menu Name: The "Rich Menu Name" property must be provided; otherwise, the API call may fail or create a menu with an undesired default name.
  • API validation skipped: If the optional external API key credential is not set, the node skips validation but still attempts the operation. This is normal behavior.

Links and References

Discussion