N8N Tools LINE icon

N8N Tools LINE

Interact with LINE Messaging API
Join our community

Actions16

Overview

This node integrates with the LINE Messaging API to manage webhook endpoints. Specifically, for the "Webhook" resource and the "Set Webhook Endpoint" operation, it allows users to configure or update the webhook endpoint URL that LINE uses to send event notifications to your application.

Common scenarios where this node is beneficial include:

  • Setting up a new webhook URL when deploying a LINE bot or service.
  • Updating the webhook URL if your server address changes.
  • Automating webhook configuration as part of CI/CD pipelines.

For example, you can use this node to programmatically set your webhook endpoint URL to https://example.com/line-webhook so that LINE events are forwarded there.

Properties

Name Meaning
Webhook Endpoint The URL of the webhook endpoint to set or test. This is the URL where LINE will send webhook events.

Output

The node outputs JSON data representing the response from the LINE Messaging API related to webhook management. For the "Set Webhook Endpoint" operation, the output typically confirms the success or failure of setting the webhook URL.

The output structure is:

{
  "json": {
    // Response data from LINE API about the webhook endpoint setting
  },
  "pairedItem": {
    "item": <index_of_input_item>
  }
}

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the LINE Messaging API.
  • Optionally uses an additional API key credential for validating subscription status via an external validation API.
  • The node depends on network access to the LINE Messaging API endpoints.
  • No special environment variables are required beyond standard n8n credential setup.

Troubleshooting

  • Invalid API Key or Subscription: If the node throws errors indicating invalid subscription or API key, verify that the provided API credentials are correct and active.
  • Webhook URL Validation Failure: Ensure the webhook URL is publicly accessible and uses HTTPS as required by LINE.
  • HTTP Errors: Network issues or incorrect URLs may cause HTTP request failures. Check connectivity and URL correctness.
  • Permission Issues: Make sure the API key has permissions to modify webhook settings.

If the node returns error messages like "N8N Tools API: Invalid subscription or API key", recheck the credentials configured in n8n.

Links and References

Discussion