Lark Email icon

Lark Email

Lark Email Management

Actions30

Overview

This node interacts with the Lark Email API to obtain information about a member of a public mailbox. It is useful in scenarios where you need to retrieve details about specific members within shared or public mailboxes, such as for managing access, auditing membership, or integrating mailbox member data into workflows.

Practical examples include:

  • Fetching member details to verify permissions before sending emails on behalf of a public mailbox.
  • Synchronizing public mailbox member information with an external user management system.
  • Automating notifications or reports based on membership changes in public mailboxes.

Properties

Name Meaning
Authentication Method of authentication to use: either "Tenant Token" or "OAuth2".
Public Mailbox Id Unique identifier or address of the public mailbox from which to obtain member information.
Member Id Unique identifier of the member within the specified public mailbox.
Options Additional optional settings:
- Use Custom Body Boolean flag indicating whether to send a custom request body (true/false).

Output

The node outputs JSON data containing detailed information about the specified public mailbox member. This typically includes member attributes such as their ID, email address, role, status, and other metadata provided by the Lark Email API.

If binary data were involved (e.g., attachments), it would be summarized here, but this operation focuses on JSON member information only.

Dependencies

  • Requires access to the Lark Suite Open API endpoint at https://open.larksuite.com/open-apis.
  • Requires valid authentication credentials, either via a Tenant Token or OAuth2 token.
  • The node expects these credentials to be configured in n8n prior to execution.

Troubleshooting

  • Invalid or missing authentication: Ensure that the correct authentication method is selected and that the corresponding credentials are properly set up in n8n.
  • Incorrect Public Mailbox Id or Member Id: Verify that the IDs provided correspond exactly to existing mailbox and member identifiers; typos or outdated IDs will cause errors.
  • API rate limits or permission issues: If the API returns errors related to permissions or rate limiting, check that the authenticated account has sufficient rights to access the mailbox member information and consider retrying after some time.
  • Use Custom Body option misuse: If enabling "Use Custom Body," ensure the custom body format matches the API requirements; otherwise, the request may fail.

Links and References

Discussion