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 allows you to modify an existing mailing list (mail group) in the Lark Email system. It is useful for updating details such as the mailing list's name, description, and permissions on who can send emails to the list. Typical use cases include managing organizational mailing lists dynamically, updating mailing list metadata after organizational changes, or automating mailing list maintenance.
For example, you could use this node to rename a mailing list after a department rebranding or change the sending permissions to restrict or open up who can send emails to that list.
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 modify. (Required) |
| Description | New description text for the mailing list. |
| Name | New display name for the mailing list. |
| Who Can Send Mail | Defines who is allowed to send mail to the mailing list. |
| Use Custom Body | Boolean flag indicating whether to send a custom JSON body instead of individual fields. |
| Custom Body | A JSON object allowing full customization of the request body sent to the API. |
Output
The node outputs the response from the Lark Email API after attempting to modify the mailing list. This output is structured as JSON and typically contains the updated mailing list information or status confirmation. There is no binary data output.
Dependencies
- Requires access to the Lark Suite Open APIs.
- Requires authentication credentials configured in n8n, either via a Tenant Token or OAuth2 token.
- The base URL for API requests is
https://open.larksuite.com/open-apis. - Proper permissions on the provided credentials to modify mailing lists.
Troubleshooting
- Invalid Mailgroup Id: If the mailing list ID or address is incorrect or does not exist, the API will return an error. Verify the mailing list identifier before running the node.
- Authentication Errors: Using invalid or expired tokens will cause authentication failures. Ensure your credentials are valid and have the necessary scopes.
- Permission Denied: If the authenticated user does not have rights to modify the mailing list, the API will reject the request.
- Malformed Custom Body: When using the custom JSON body option, ensure the JSON structure matches the API expectations; otherwise, the request may fail.
- Empty Required Fields: The mailing list ID is required; omitting it will cause the node to error out.
Links and References
- Lark Suite Open API Documentation
- Managing Mailing Lists with Lark Email API (example section)