Lark Messenger icon

Lark Messenger

Lark Messenger Management

Actions38

Overview

This node interacts with the Lark Messenger platform to manage group members within chat groups. Specifically, the "Obtain Group Member List" operation retrieves the list of members in a specified group chat. This is useful for scenarios where you need to programmatically access or audit group membership, such as syncing group members with another system, sending targeted messages, or managing permissions.

Practical examples:

  • Automatically fetching all members of a project discussion group to send notifications.
  • Auditing group membership to ensure compliance with organizational policies.
  • Integrating group member data into CRM or HR systems.

Properties

Name Meaning
Authentication Method of authenticating API requests. Options: Tenant Token (using a tenant-level API token), OAuth2 (using OAuth2 authentication flow).
Chat Id The unique identifier of the group chat whose members are to be listed. Required to specify which group's members to retrieve.
Options Additional optional settings. Currently supports: Use Custom Body (boolean) - whether to send a custom request body instead of the default format.

Output

The node outputs JSON data containing the list of group members retrieved from the Lark Messenger API. The structure typically includes member details such as user IDs, names, roles, and other metadata related to each group member.

If binary data were involved (e.g., profile pictures), it would be included in a separate binary output field, but this operation focuses on JSON member lists only.

Dependencies

  • Requires an active connection to the Lark Messenger API.
  • Requires either a valid tenant token credential or OAuth2 authentication configured in n8n.
  • Network access to https://open.larksuite.com/open-apis must be available.
  • Proper permissions granted to the API credentials to read group member information.

Troubleshooting

  • Invalid or missing Chat Id: Ensure the Chat Id is correctly provided and corresponds to an existing group chat.
  • Authentication errors: Verify that the selected authentication method is properly configured and the credentials are valid and have sufficient permissions.
  • API rate limits or network issues: If requests fail intermittently, check network connectivity and API usage limits.
  • Use Custom Body option misuse: If enabled without proper formatting, the request may fail. Only enable if you intend to provide a fully customized request body.

Common error messages:

  • Unauthorized or 401 errors indicate invalid or expired credentials.
  • 404 Not Found may indicate the Chat Id does not exist or is inaccessible.
  • 400 Bad Request can result from malformed input or incorrect use of the custom body option.

Links and References

Discussion