Actions16
- Messages Actions
- Profile Actions
- Rich Menu Actions
- Webhook Actions
Overview
This node enables interaction with the LINE Messaging API, specifically allowing retrieval of user profile information within the "Profile" resource. The "Get Profile" operation fetches the profile details of a specified LINE user by their User ID.
Common scenarios where this node is beneficial include:
- Personalizing chatbot responses by obtaining user display names and profile pictures.
- Integrating LINE user data into CRM or customer support systems.
- Verifying user identity or gathering user metadata for analytics.
For example, you can use this node to get the profile of a user who just sent a message to your LINE bot, then greet them by name or customize the conversation based on their profile info.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the LINE user whose profile you want to retrieve. |
Output
The node outputs JSON data representing the user's profile information as returned by the LINE Messaging API. This typically includes fields such as:
displayName: The user's display name.userId: The user's unique LINE ID.pictureUrl: URL to the user's profile picture (if available).statusMessage: The user's status message (if set).
No binary data output is produced 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 if not provided, it skips validation.
- The node depends on the bundled
LineApihelper class to perform API requests.
Troubleshooting
- Invalid subscription or API key error: If the node throws an error about invalid subscription or API key, verify that the API key credential is correctly configured and active.
- User ID missing or incorrect: Ensure the User ID input property is correctly set; otherwise, the API call will fail.
- Permission issues: The LINE Messaging API may restrict access to certain profile information depending on the bot's permissions and user privacy settings.
- Network or API errors: General HTTP errors from the LINE API should be checked for rate limits, connectivity, or service availability.