Actions16
- Messages Actions
- Profile Actions
- Rich Menu Actions
- Webhook Actions
Overview
The node integrates with the LINE Messaging API to perform various operations related to LINE's Rich Menu feature. Specifically, for the "Set Default Rich Menu" operation under the "Rich Menu" resource, it sets a specified rich menu as the default one for the LINE bot account. This means that the chosen rich menu will be shown by default to all users who have not been assigned a personalized rich menu.
This node is beneficial in scenarios where you want to manage and automate the configuration of your LINE bot's user interface menus programmatically within an n8n workflow. For example, after creating or updating multiple rich menus, you can use this node to set which menu should be the default for all users.
Properties
| Name | Meaning |
|---|---|
| Rich Menu ID | The identifier of the rich menu to set as the default. This must be a valid existing rich menu ID. |
Output
The node outputs JSON data representing the response from the LINE Messaging API when setting the default rich menu. Typically, this response confirms the success of the operation or provides error details if the operation failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authentication with the external service managing the LINE Messaging API requests.
- Optionally uses a secondary API key credential for validation via an external "N8N Tools API" service to verify subscription and API key validity before executing the main operation.
- The node depends on the bundled
LineApiclass (from the importedline-apimodule) to interact with the LINE Messaging API endpoints. - Proper configuration of credentials and permissions to access and modify LINE rich menus is necessary.
Troubleshooting
- Invalid Subscription or API Key: If the external validation fails with HTTP status 401 or 403, the node throws an error indicating invalid subscription or API key. Ensure that the API keys are correctly configured and active.
- Unknown Operation Error: If an unsupported operation name is provided, the node throws an error stating "Unknown operation". Verify that the operation parameter is set correctly to "setDefaultRichMenu".
- Rich Menu ID Issues: Providing an invalid or non-existent rich menu ID will cause the LINE API to return an error. Confirm that the rich menu ID exists and is correct.
- Credential Not Found: If the required credentials are missing, the node skips validation but may fail later when calling the LINE API. Make sure all necessary credentials are supplied.
- Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if one item fails, returning error details in the output JSON.