Actions4
Overview
This node interacts with the Line Messaging API, specifically to retrieve profile information of a user when using the "Get Profile" operation. It is useful in scenarios where you need to fetch details about a Line user, such as their display name, status message, or profile picture URL, based on their user ID. Practical examples include personalizing messages by addressing users by their names or displaying user profile data within an application.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose profile you want to retrieve (required string). |
Output
The output contains a JSON object representing the user's profile information retrieved from the Line Messaging API. This typically includes fields such as the user's display name, user ID, profile picture URL, and status message. The node does not output binary data for this operation.
Example output structure (simplified):
{
"userId": "U4af4980629...",
"displayName": "John Doe",
"pictureUrl": "https://profile.line-scdn.net/...",
"statusMessage": "Hello, world!"
}
Dependencies
- Requires an API key credential for authenticating with the Line Messaging API.
- The node must be configured with valid credentials that allow access to the Line Messaging service.
- Network connectivity to the Line Messaging API endpoints is necessary.
Troubleshooting
Common issues:
- Invalid or missing User ID: Ensure the User ID is correctly provided and corresponds to a valid Line user.
- Authentication errors: Verify that the API key credential is correctly set up and has the necessary permissions.
- Network errors: Check internet connectivity and firewall settings that might block access to the Line Messaging API.
Common error messages:
- Unauthorized or authentication failed: Indicates invalid or expired API credentials; reconfigure the API key.
- User not found: The provided User ID does not exist or is incorrect; verify the User ID.
- Rate limit exceeded: Too many requests sent in a short period; implement retry logic or reduce request frequency.