Lark Messenger icon

Lark Messenger

Lark Messenger Management

Overview

The node "Lark Messenger" provides management capabilities for Lark Messenger, a communication platform. Specifically, the operation "Search For Groups Visible To A User Or Bot" allows users to find groups that are accessible or visible to a particular user or bot within the Lark environment. This is useful in scenarios where you want to programmatically discover group chats or channels that a user or bot can interact with, such as for automation workflows that involve messaging, notifications, or group management.

Practical examples include:

  • Automatically listing all groups a bot can post messages to.
  • Fetching groups visible to a user to display options in a UI.
  • Integrating group data into other systems for reporting or analytics.

Properties

Name Meaning
Authentication Method of authenticating API requests. Options: "Tenant Token" or "OAuth2".
Options Additional optional settings for the request.
- Use Custom Body Boolean flag indicating whether to send a custom request body instead of default format.

Output

The node outputs JSON data representing the groups visible to the specified user or bot. The structure typically includes details about each group such as group ID, name, and possibly metadata like member count or description. If binary data were involved (not indicated here), it would represent attachments or media related to groups, but this node focuses on JSON group information.

Dependencies

  • Requires an API authentication token, either via a Tenant Token or OAuth2 credentials configured in n8n.
  • Connects to the Lark Suite Open APIs at https://open.larksuite.com/open-apis.
  • No additional external dependencies beyond the configured credentials and network access to Lark's API.

Troubleshooting

  • Authentication errors: Ensure that the provided API token or OAuth2 credentials are valid and have sufficient permissions to query group information.
  • Empty results: Verify that the user or bot actually has visibility to any groups; otherwise, the response will be empty.
  • Network issues: Confirm that n8n can reach the Lark API endpoint without firewall or proxy blocking.
  • Custom body usage: If enabling "Use Custom Body," ensure the custom payload matches the expected API schema to avoid request failures.

Links and References

Discussion