Actions30
- Mail Group Actions
- Mail Group Member Actions
- Mail Group Permission Member Actions
- Mail Group Alias Actions
- Public Mailbox Actions
- Public Mailbox Member Actions
- Public Mailbox Alias Actions
Overview
This node, named "Lark Email," provides management capabilities for Lark email-related resources. Specifically, the "Delete A Mailing List" operation under the "Mail Group" resource allows users to delete an existing mailing list by specifying its ID or address. This is useful in scenarios where mailing lists become obsolete, need to be cleaned up, or require removal due to organizational changes.
Practical examples include:
- Automatically removing mailing lists that are no longer active.
- Cleaning up test or temporary mailing groups after a project ends.
- Managing mailing lists programmatically as part of user lifecycle automation.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" or "OAuth2". |
| Mailgroup Id | The unique identifier or email address of the mailing list to delete (required). |
| Options | Additional options for the request: |
| - Use Custom Body | Boolean flag indicating whether to send a custom request body instead of the default. |
Output
The node outputs JSON data representing the response from the Lark API after attempting to delete the mailing list. Typically, this will include status information indicating success or failure of the deletion operation.
If the node supports binary data output, it would represent any file or attachment data returned by the API, but in this case, the operation deals with deletion and thus primarily returns JSON status responses.
Dependencies
- Requires access to the Lark Suite Open API endpoint at
https://open.larksuite.com/open-apis. - Requires valid authentication credentials, either via a Tenant Token or OAuth2 token.
- Proper configuration of these credentials within n8n is necessary for successful API calls.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens can cause authorization failures.
- Providing an incorrect or non-existent mailing list ID will result in errors indicating the resource was not found.
- Network connectivity issues may prevent reaching the Lark API endpoint.
Error Messages:
- Authorization errors typically indicate invalid credentials; re-authenticate or refresh tokens.
- "Mailing list not found" errors suggest verifying the mailing list ID or address.
- API rate limits might cause temporary blocking; wait and retry later.