Actions7
Overview
This node integrates with the LINE Messaging API to perform various messaging and user profile operations within LINE chats. Specifically, for the "Get Group Chat Member Profile" operation, it retrieves detailed profile information about a specific member of a group chat using the group's ID and the user's ID.
Common scenarios where this node is beneficial include:
- Fetching user profile details in group chats for personalized messaging or analytics.
- Automating responses or workflows based on group member attributes.
- Managing group chat members by accessing their profile data programmatically.
Practical example:
- After receiving a webhook event indicating a new message in a group chat, use this node to get the sender's profile information (such as display name and status message) to customize your bot's reply.
Properties
| Name | Meaning |
|---|---|
| Group ID | The unique identifier of the group chat. Found in the source object of webhook event objects. |
| User ID | The unique identifier of the user within the group chat. This ID comes from webhook events and should not be confused with the general LINE user ID. |
Output
The output JSON contains the profile information of the specified group chat member. Typical fields returned may include:
displayName: The member's display name in the group.userId: The unique user ID within the group.pictureUrl: URL to the member's profile picture.statusMessage: The member's status message.
The exact structure depends on the LINE Messaging API response for group member profiles.
No binary data output is produced by this operation.
Dependencies
- Requires an active LINE Messaging API channel access token credential configured in n8n.
- Uses the official LINE Bot SDK (
@line/bot-sdk) internally to communicate with the LINE Messaging API. - The node expects valid group and user IDs obtained from LINE webhook events or other sources.
Troubleshooting
- Missing or invalid credentials: If the node throws an error about missing authentication, ensure that the LINE Messaging API credential is properly set up with a valid channel access token.
- Invalid Group ID or User ID: Errors may occur if the provided group or user IDs are incorrect or no longer valid. Verify these IDs come directly from LINE webhook events.
- API rate limits or network issues: The LINE Messaging API enforces rate limits; excessive requests may cause failures. Check network connectivity and API usage quotas.
- User not found in group: If the user ID does not belong to the specified group, the API will return an error. Confirm the user is a current member of the group.