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
The node "Lark Email" provides integration with Lark's email management system. Specifically, the operation "Obtain A Public Mailbox" allows users to retrieve details about a public mailbox by specifying its unique identifier or address. This is useful in scenarios where automated workflows need to access shared mailboxes for reading emails, monitoring incoming messages, or managing mailbox settings without manual intervention.
Practical examples include:
- Automatically fetching metadata or configuration of a public mailbox before processing its emails.
- Integrating with team collaboration tools that rely on shared mailboxes.
- Building notification systems that trigger based on public mailbox activity.
Properties
Name | Meaning |
---|---|
Authentication | Method to authenticate API requests; options are "Tenant Token" or "OAuth2". |
Public Mailbox Id | Unique identifier or address of the public mailbox to obtain information about (required). |
Options | Additional optional settings: |
- Use Custom Body | Boolean flag indicating whether to send a custom request body instead of the default one. |
Output
The node outputs JSON data representing the details of the requested public mailbox. This typically includes mailbox metadata such as its ID, address, display name, and possibly other configuration or status fields returned by the Lark email API.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to Lark's Open API endpoint at
https://open.larksuite.com/open-apis
. - Requires authentication via either:
- A tenant token credential, or
- An OAuth2 credential.
- The node expects these credentials to be configured within n8n prior to execution.
Troubleshooting
Common issues:
- Invalid or missing public mailbox ID will cause the API call to fail.
- Incorrect or expired authentication tokens will result in authorization errors.
- Network connectivity problems can prevent reaching the Lark API endpoint.
Error messages and resolutions:
- 401 Unauthorized: Check that the provided authentication token is valid and has not expired.
- 404 Not Found: Verify that the public mailbox ID or address is correct and exists.
- 400 Bad Request: If using the "Use Custom Body" option, ensure the custom body format matches API expectations.
- Network errors: Confirm internet connectivity and that no firewall blocks the API URL.
Links and References
- Lark Open API Documentation
- Lark Email API Reference (for detailed mailbox operations)