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
The "Delete A Group" operation in the Lark Messenger node allows users to delete a specific group chat by providing its unique group ID (Chat Id). This operation is useful for managing group chats within the Lark Messenger platform, such as removing obsolete or inactive groups to keep the workspace organized.
Practical examples include:
- Automatically deleting project-specific group chats once a project is completed.
- Cleaning up temporary discussion groups created for events or meetings.
- Managing group lifecycle programmatically based on business rules.
Properties
Name | Meaning |
---|---|
Authentication | Method of authenticating API requests. Options: Tenant Token, OAuth2. |
Chat Id | The unique identifier of the group chat to be deleted. Required to specify which group to remove. |
Options | Additional optional settings. |
- Use Custom Body | Boolean flag indicating whether to send a custom request body instead of the default one. Typically false for this operation. |
Output
The output of this operation typically contains a JSON response from the Lark Messenger API confirming the deletion status of the specified group. The exact structure depends on the API response but generally includes success indicators or error messages.
No binary data output is expected from this operation.
Dependencies
- Requires an active connection to the Lark Messenger API.
- Requires authentication via either a Tenant Token or OAuth2 credentials configured in n8n.
- Network access to
https://open.larksuite.com/open-apis
is necessary.
Troubleshooting
- Invalid Chat Id: If the provided group ID does not exist or is incorrect, the API will return an error indicating the group was not found. Verify the Chat Id value.
- Authentication Errors: Using invalid or expired credentials will cause authentication failures. Ensure that the Tenant Token or OAuth2 token is valid and has sufficient permissions.
- Permission Denied: The authenticated user or token may lack rights to delete the specified group. Check API permissions and scopes.
- API Rate Limits: Excessive requests might trigger rate limiting. Implement retries with backoff if needed.
- Use Custom Body Misuse: Setting "Use Custom Body" to true without proper formatting may cause request errors. Usually, this should remain false unless advanced customization is required.
Links and References
- Lark Messenger API Documentation — Details on Chat Id and group management endpoints.
- n8n Documentation on Credentials — How to configure API authentication in n8n.