Actions7
Overview
This node integrates with the Line Messaging API to perform various messaging and group-related operations. Specifically, for the "Get Group Chat Member User IDs" operation, it retrieves the list of user IDs of all members in a specified group chat. This is useful when you want to programmatically access or manage group participants, such as sending targeted messages, analyzing group membership, or syncing group data with other systems.
Practical examples include:
- Fetching all member IDs from a group chat to send personalized notifications.
- Auditing group membership for compliance or moderation purposes.
- Integrating group member data into CRM or marketing platforms.
Properties
| Name | Meaning |
|---|---|
| Group ID | The unique identifier of the group chat whose member user IDs you want to retrieve. This ID is typically found in webhook event objects related to group chats. |
Output
The output is a JSON object containing the list of user IDs of the group chat members. The structure corresponds directly to the response from the Line Messaging API's method for fetching group member IDs.
Example output structure (simplified):
{
"memberIds": [
"Uxxxxxxxxxxxxxx1",
"Uxxxxxxxxxxxxxx2",
"Uxxxxxxxxxxxxxx3"
]
}
No binary data is produced by 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 Messaging 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 API token is missing or incorrect, the node will throw an error indicating no authentication was provided. Ensure that the API key credential is correctly set up and has the necessary permissions.
- Invalid Group ID: Providing an incorrect or non-existent group ID will result in API errors or empty results. Verify the group ID from webhook events or the Line platform.
- API rate limits: Excessive calls to the Line Messaging API may lead to rate limiting. Implement retries or backoff strategies if needed.
- Network issues: Connectivity problems can cause request failures. Check network status and proxy settings if applicable.