Lark Email icon

Lark Email

Lark Email Management

Overview

This node interacts with the Lark Email service to obtain detailed information about a specific member of a mailing list (mail group). It is useful in scenarios where you need to retrieve membership details such as status, subscription info, or other metadata related to an individual member within a mail group. For example, it can be used in automated workflows to verify if a user is part of a mailing list before sending targeted communications or managing subscriptions.

Properties

Name Meaning
Authentication Method of authenticating API requests. Options: "Tenant Token" or "OAuth2".
Mailgroup Id The unique identifier or email address of the mailing list from which to get member info.
Member Id The unique identifier of the member within the specified mailing list.
Options Additional optional settings. Currently supports:
- Use Custom Body Boolean flag indicating whether to send a custom request body instead of default format.

Output

The node outputs JSON data containing the detailed information of the specified mailing list member. This typically includes fields such as member ID, email, subscription status, and any other metadata returned by the Lark Email API for that member. The output does not include binary data.

Dependencies

  • Requires access to the Lark Email API.
  • Needs either a Tenant Token or OAuth2 authentication configured in n8n credentials.
  • The base URL for API requests is https://open.larksuite.com/open-apis.
  • Proper permissions on the Lark platform to read mailing list member information.

Troubleshooting

  • Invalid Credentials: If authentication fails, ensure that the provided Tenant Token or OAuth2 credentials are valid and have sufficient permissions.
  • Member Not Found: Errors may occur if the specified member ID does not exist in the given mail group. Verify the correctness of both Mailgroup Id and Member Id.
  • API Rate Limits: Frequent requests might hit rate limits imposed by Lark API; consider adding delays or handling retries.
  • Use Custom Body Misconfiguration: If enabling "Use Custom Body", ensure the custom body format matches API expectations to avoid request errors.

Links and References

Discussion