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 enables managing members of mail groups within the Lark Email system. Specifically, the "Delete A Mailing List Member" operation allows users to remove a specific member from a designated mail group by providing the mail group's identifier and the member's unique ID. This is useful in scenarios where mailing lists need to be maintained dynamically, such as removing former employees or unsubscribed users from internal communication groups.
Practical examples include:
- Automatically cleaning up mailing lists when users leave an organization.
- Managing subscription lists by removing users who opt out.
- Integrating with HR systems to sync mailing list membership.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests; options are "Tenant Token" or "OAuth2". |
| Mailgroup Id | The unique identifier or email address of the mail group from which a member will be removed. |
| Member Id | The unique identifier of the member to delete from the specified mail group. |
| Options | Additional optional settings; currently supports: |
| - 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 result of the deletion operation. Typically, this includes confirmation of successful removal or error details if the operation failed. There is no indication that binary data is output by this node.
Dependencies
- Requires authentication via either a Tenant Token or OAuth2 credentials for accessing the Lark Suite API.
- The node communicates with the Lark Suite Open APIs at
https://open.larksuite.com/open-apis. - Proper configuration of these credentials within n8n is necessary for successful execution.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens can cause authorization failures.
- Incorrect Mailgroup Id or Member Id values will result in errors indicating that the resource was not found.
- Network connectivity issues may prevent reaching the Lark Suite API endpoint.
Error Messages:
- Authorization errors typically suggest checking the validity and permissions of the provided credentials.
- Not found errors indicate verifying the correctness of the mail group and member identifiers.
- If using the "Use Custom Body" option incorrectly, the API might reject the request due to malformed payloads.