Lark Email icon

Lark Email

Lark Email Management

Actions30

Overview

This node interacts with a mailing list permission system to obtain details about a specific member who has the permission to send emails to mailing list addresses. It is useful in scenarios where you need to verify or retrieve information about authorized senders within an email group, such as managing access control for corporate mailing lists or automating workflows that depend on sender permissions.

For example, an organization might use this node to programmatically check if a particular user is allowed to send emails to a certain mailing list before sending automated notifications or newsletters.

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 query.
Permission Member Id The unique identifier of the member whose permission details are being obtained.
Options Additional optional settings:
• Use Custom Body (boolean) - whether to send a custom request body.

Output

The node outputs JSON data containing the details of the specified permission member who can send emails to the mailing list. This typically includes member identification and permission attributes relevant to their ability to send emails. The output structure is designed to be consumed by subsequent nodes for further processing or decision-making.

No binary data output is indicated.

Dependencies

  • Requires an API key credential or OAuth2 token for authentication with the external mailing list service.
  • The node communicates with the Lark Suite Open APIs at https://open.larksuite.com/open-apis.
  • Proper configuration of credentials in n8n is necessary to authenticate requests.

Troubleshooting

  • Common issues:

    • Invalid or missing mailing list ID or permission member ID will cause errors.
    • Authentication failures due to incorrect or expired tokens.
    • Network connectivity issues preventing access to the Lark Suite API endpoint.

  • Error messages and resolutions:

    • Unauthorized / 401 errors: Check that the provided API key or OAuth2 token is valid and has not expired.
    • Not Found / 404 errors: Verify that the mailing list ID and permission member ID are correct and exist.
    • Bad Request / 400 errors: Ensure all required parameters are provided and correctly formatted.
    • If using the "Use Custom Body" option, ensure the custom body content is valid JSON and matches the API expectations.

Links and References

Discussion