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, named "Lark Email," is designed to manage email-related operations within the Lark platform, specifically focusing on public mailbox members in this context. The operation "Obtain Public Mailbox Members In Batch" allows users to retrieve multiple members of a specified public mailbox at once. This can be particularly useful for administrators or automation workflows that need to audit, synchronize, or manage access permissions for shared mailboxes efficiently.
Practical examples include:
- Automatically fetching all members of a public mailbox to update an internal directory.
- Integrating with other systems to synchronize mailbox membership.
- Auditing mailbox members periodically for compliance or security reviews.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: Tenant Token, OAuth2 |
| Public Mailbox Id | The unique identifier or email address of the public mailbox whose members are to be fetched |
| Options | Additional optional settings: - Use Custom Body (boolean): Whether to send a custom request body instead of default |
Output
The output will contain JSON data representing the list of members belonging to the specified public mailbox. Each member's details typically include identifiers and metadata relevant to their membership status. The exact structure depends on the Lark API response but generally includes user IDs, roles, and possibly contact information.
If binary data were involved (not indicated here), it would represent attachments or similar content, but this operation focuses solely on JSON member data.
Dependencies
- Requires valid authentication via either a Tenant Token or OAuth2 credentials configured in n8n.
- Depends on access to the Lark Suite Open APIs endpoint
https://open.larksuite.com/open-apis. - Proper permissions must be granted to the authenticated account to read public mailbox member information.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect or non-existent Public Mailbox Id causing "not found" errors.
- Insufficient permissions for the authenticated user to access mailbox member data.
Error Messages:
- 401 Unauthorized: Check that the API credentials are correct and have not expired.
- 404 Not Found: Verify the Public Mailbox Id is accurate and exists.
- 403 Forbidden: Ensure the authenticated user has permission to view the mailbox members.
Resolving these usually involves verifying credentials, mailbox identifiers, and user permissions within the Lark admin console.
Links and References
- Lark Suite Open API Documentation
- Managing Public Mailboxes in Lark (general guidance on public mailboxes)