Actions7
Overview
This node integrates with the Line Messaging API to perform various messaging-related operations. Specifically, for the "Get User Profile" operation, it retrieves the profile information of a user based on their User ID. This is useful in scenarios where you want to fetch details about a user who interacted with your Line bot, such as displaying their display name or profile picture within your workflow.
Practical examples include:
- Fetching user profile data after receiving a webhook event to personalize responses.
- Retrieving group chat member profiles to manage group interactions.
- Accessing user information for logging or analytics purposes.
Properties
| Name | Meaning |
|---|---|
| User ID | The unique identifier of the user whose profile is to be retrieved. This ID comes from webhook events and should not be confused with the general LINE ID. |
Output
The output contains a JSON object representing the user's profile information as returned by the Line Messaging API. Typical fields may include the user's display name, userId, profile picture URL, and status message.
Example output structure (simplified):
{
"userId": "Uxxxxxxxxxxxxxx",
"displayName": "User Name",
"pictureUrl": "https://profile.line-scdn.net/...",
"statusMessage": "Hello, world!"
}
No binary data output is produced for this operation.
Dependencies
- Requires an active connection to the Line Messaging API using a valid API authentication token (channel access token).
- The node depends on the official Line SDK for JavaScript to interact with the API.
- Proper credentials must be configured in n8n to authenticate requests.
Troubleshooting
- Missing or invalid credentials: If the channel access token is missing or incorrect, the node will throw an authentication error. Ensure that the API key credential is correctly set up in n8n.
- Invalid User ID: Using an incorrect or malformed User ID (not the one from webhook events) will result in errors or empty responses. Always use the User ID provided by Line webhook events.
- API rate limits: Excessive requests to the Line API might lead to rate limiting. Implement appropriate error handling or throttling in workflows.
- Network issues: Connectivity problems can cause request failures; verify network access to the Line API endpoints.