N8N Tools LINE icon

N8N Tools LINE

Interact with LINE Messaging API
Join our community

Actions16

Overview

The "Delete Rich Menu" operation in this node allows users to delete a specific rich menu from their LINE Messaging API setup. Rich menus are customizable menus that appear in the LINE chat interface, providing interactive options for users. This operation is useful when you want to remove outdated or unused rich menus to keep your LINE bot's interface clean and relevant.

Practical scenarios include:

  • Removing a promotional menu after a campaign ends.
  • Cleaning up test or temporary rich menus created during development.
  • Managing multiple rich menus dynamically by deleting those no longer needed.

Properties

Name Meaning
Rich Menu ID The unique identifier of the rich menu to be deleted.

Output

The output JSON contains the response from the LINE Messaging API after attempting to delete the specified rich menu. Typically, this will be an empty object or confirmation indicating successful deletion. If an error occurs, the output will contain an error message describing the issue.

No binary data is output by this operation.

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), but this validation is skipped if credentials are not found.
  • The node depends on the bundled LineApi class which handles communication with the LINE Messaging API endpoints.

Troubleshooting

  • Invalid Rich Menu ID: If the provided Rich Menu ID does not exist or is malformed, the API will return an error. Verify the ID is correct.
  • Authentication Errors: If the API key credential is missing or invalid, the node will fail with an authentication error. Ensure valid credentials are configured.
  • Permission Issues: The API key must have permission to delete rich menus. Lack of permissions will cause errors.
  • Network or API Endpoint Issues: Connectivity problems or incorrect base URLs can cause request failures.
  • Validation Failures: If the optional external validation fails due to invalid subscription or API key, the node throws a descriptive error. Check credentials for the external validation service.

To resolve errors, verify all input parameters, ensure proper credentials are set, and check network connectivity.

Links and References

Discussion