Actions38
- Message Actions
- Message Buzz Message Actions
- Message Batch Message Actions
- Message Image Actions
- Message File Actions
- Message Message Card Actions
- Message Message Reaction Actions
- Group Actions
- Group Group Member Actions
- Group Group Announcement Actions
Overview
This node, named "Lark Messenger," is designed to interact with the Lark messaging platform, specifically focusing on managing groups and messages within Lark. The particular operation "Obtain The List Of Groups With The User Or Bot" allows users to retrieve a list of groups that the authenticated user or bot is part of. This can be useful for scenarios such as monitoring group memberships, automating group-based notifications, or integrating group data into other workflows.
Practical examples include:
- Automatically fetching all groups a bot belongs to in order to send targeted announcements.
- Synchronizing group membership information with an external CRM or database.
- Triggering workflows based on group activity or presence.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate 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. |
Output
The node outputs JSON data representing the list of groups associated with the user or bot. Each item in the output typically contains details about a group such as its ID, name, type, and possibly metadata like creation time or member count (exact fields depend on the Lark API response).
If binary data were involved (e.g., attachments), it would be included in a separate binary property, but this operation focuses on JSON group data only.
Dependencies
- Requires access to the Lark Open API at
https://open.larksuite.com/open-apis. - Needs authentication via either:
- A Tenant Token credential (an API key/token scoped to a tenant).
- An OAuth2 credential (user or bot authorization token).
- Proper configuration of these credentials in n8n is necessary for successful API calls.
Troubleshooting
- Authentication errors: If the node fails due to invalid or missing credentials, verify that the correct authentication method is selected and that the credentials are valid and have sufficient permissions.
- Empty group list: If no groups are returned, ensure the authenticated user or bot is actually a member of any groups.
- API rate limits or connectivity issues: Network problems or hitting API rate limits may cause failures; check network connectivity and consider retry logic.
- Custom body usage: If "Use Custom Body" is enabled but the body is malformed or incomplete, the API may reject the request. Validate the custom body format carefully.