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 integrates with Lark Messenger to manage group chats, specifically allowing the removal of users or bots from a group chat. It is useful in scenarios where group membership needs to be controlled dynamically, such as moderating chat participants, managing team access, or automating user removals based on external triggers.
For example, an organization might use this node to automatically remove users who have left a project from the relevant group chat, or to revoke bot access when a service is deprecated.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: "Tenant Token" (using a tenant-level API token) or "OAuth2" (using OAuth2 flow). |
| Chat Id | The unique identifier of the group chat from which users or bots will be removed. |
| Options | Additional optional settings. Currently supports: - Use Custom Body: Whether to send a custom request body instead of the default format. |
Output
The node outputs JSON data representing the response from the Lark Messenger API after attempting to remove users or bots from the specified group chat. This typically includes status information about the operation's success or failure and any relevant metadata returned by the API.
No binary data output is indicated.
Dependencies
- Requires valid authentication credentials for Lark Messenger API, either via a tenant token or OAuth2.
- Needs network access to
https://open.larksuite.com/open-apis. - Proper configuration of authentication credentials within n8n is necessary before using this node.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens can cause authorization failures.
- Incorrect or malformed Chat Ids will result in errors indicating the group was not found.
- Using the "Use Custom Body" option incorrectly may lead to malformed requests and API errors.
Error Messages:
- Authorization errors typically indicate issues with the provided API key or OAuth2 token; refreshing or reconfiguring credentials usually resolves these.
- "Chat not found" or similar errors suggest verifying the Chat Id value.
- API rate limits may cause temporary failures; implementing retries or backoff strategies can help.
Links and References
- Lark Messenger Group ID Description (as referenced in the property description)