Lark Email icon

Lark Email

Lark Email Management

Actions30

Overview

This node enables managing email permissions within Lark's mailing groups, specifically allowing the creation of members who have permission to send emails to mailing list addresses. It is useful in scenarios where an organization wants to control which users or departments can send emails to a particular mailing list, ensuring proper access and communication flow.

Practical examples include:

  • Adding a new user to a mailing list with send permissions.
  • Granting an entire department the ability to send emails to a specific group.
  • Automating permission management for mailing lists based on organizational changes.

Properties

Name Meaning
Authentication Method of authentication to use: either "Tenant Token" or "OAuth2".
Mailgroup Id The ID or address of the mailing list to which the member will be added.
Department Id (Optional) The ID of the department to grant send permissions to.
Type (Optional) The type of member being added (e.g., user or department).
User Id (Optional) The ID of the user to grant send permissions to.
Custom Body A JSON object to provide a custom request body instead of using the standard fields.
Options > Use Custom Body Boolean flag to indicate whether to use the custom JSON body for the request.

Output

The node outputs JSON data representing the response from the Lark API after attempting to create the member with send permissions. This typically includes confirmation details about the newly created member or error information if the operation failed.

If binary data were involved (not indicated here), it would represent attachments or similar content, but this node focuses on JSON responses related to permission management.

Dependencies

  • Requires an active connection to Lark's Open API.
  • Needs either a Tenant Token or OAuth2 credentials configured in n8n for authentication.
  • Network access to https://open.larksuite.com/open-apis is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing mailing list ID (Mailgroup Id) will cause the API call to fail.
    • Incorrect or expired authentication tokens will result in authorization errors.
    • Providing both User Id and Department Id incorrectly or omitting required fields may lead to bad request errors.
    • Using a malformed custom JSON body can cause request failures.

  • Error messages:

    • Authorization errors usually indicate problems with the provided credentials; verify and refresh tokens as needed.
    • Validation errors often point to missing or invalid parameters; ensure all required fields are correctly filled.
    • API rate limits might cause temporary failures; retry after some time if rate-limited.

Links and References

Discussion