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 resources within the Lark platform. Specifically, for the resource Public Mailbox Alias and operation Obtain All Public Mailbox Aliases, it retrieves all aliases associated with a given public mailbox. This can be useful in scenarios where an organization wants to list or audit all alternative email addresses (aliases) linked to a shared or public mailbox.
Practical examples include:
- Fetching all aliases of a public mailbox to display them in an admin dashboard.
- Synchronizing alias information with other systems or directories.
- Validating alias existence before sending emails or configuring routing rules.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" or "OAuth2". |
| Public Mailbox Id | The identifier or email address of the public mailbox whose aliases are to be obtained. |
| Options > Use Custom Body | Boolean flag indicating whether to send a custom request body (true/false). Defaults to false. |
Output
The node outputs JSON data containing the list of all aliases associated with the specified public mailbox. The structure typically includes details such as alias email addresses and possibly metadata related to each alias.
If binary data were involved (not indicated here), it would represent attachments or files related to the mailbox aliases, but this node focuses on JSON data output only.
Dependencies
- Requires access to the Lark platform's Open API endpoint at
https://open.larksuite.com/open-apis. - Needs valid authentication credentials, either via a Tenant Token or OAuth2 token.
- Proper configuration of these credentials in n8n is necessary for successful API calls.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens will cause authorization failures.
- Incorrect or missing Public Mailbox Id will result in errors or empty results.
- Network connectivity issues may prevent reaching the Lark API endpoint.
Error Messages:
- Authorization errors typically indicate invalid credentials; re-authenticate or refresh tokens.
- "Mailbox not found" or similar messages suggest the provided Public Mailbox Id is incorrect.
- API rate limits might cause temporary blocking; wait and retry later.
Links and References
- Lark Open Platform API Documentation
- Lark Email Management API Reference (replace with actual section if available)