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 Lark email functionalities within n8n workflows. Specifically, the "Obtain Public Mailboxes In Batch" operation under the "Public Mailbox" resource allows users to retrieve multiple public mailboxes at once from the Lark platform. This can be useful in scenarios where an organization needs to synchronize or audit public mailbox information, automate email routing setups, or integrate mailbox data into other systems.
Practical examples include:
- Fetching a list of all public mailboxes for reporting or monitoring purposes.
- Automating the setup of email forwarding rules based on mailbox data.
- Integrating mailbox details into CRM or helpdesk tools for unified communication management.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: "Tenant Token" or "OAuth2". |
| Options | Additional optional settings for the request. |
| useCustomBody | Boolean flag indicating whether to send a custom request body instead of the default one. |
Output
The node outputs JSON data containing the batch of public mailboxes retrieved from the Lark platform. The structure typically includes details about each mailbox such as mailbox ID, name, and related metadata. If binary data were involved (e.g., attachments), it would be summarized here, but this operation focuses on JSON mailbox data only.
Dependencies
- Requires access to the Lark Suite Open APIs.
- Needs either a Tenant Token or OAuth2 credentials configured in n8n for authentication.
- The base URL for API requests is
https://open.larksuite.com/open-apis. - Proper permissions on the Lark account to read public mailbox information.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials and has sufficient permissions.
- API request failures: Check network connectivity and verify that the Lark API service is operational.
- Invalid custom body usage: If "Use Custom Body" is enabled, ensure the custom body format matches the API specification; otherwise, the request may fail.
- Empty or incomplete results: Confirm that the account has public mailboxes available and that any filters or options are set correctly.