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 allows you to create a member in a public mailbox within the Lark Email system. It is useful for managing shared mailboxes by adding users who can access and manage emails collectively. Typical scenarios include team inbox management, customer support mailboxes, or any situation where multiple users need shared email access.
For example, you might use this node to add a new team member to a support mailbox so they can receive and respond to customer inquiries.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: Tenant Token, OAuth2 |
| Public Mailbox Id | Unique identifier or address of the public mailbox where the member will be added (required) |
| Type | The type of member being added (string value sent in request body) |
| User Id | Identifier of the user to add as a member (string value sent in request body) |
| Use Custom Body | Boolean option to specify whether to send a custom JSON body instead of the standard parameters |
| Custom Body | JSON object representing a custom request body to send if "Use Custom Body" is enabled |
Output
The node outputs JSON data representing the response from the Lark Email API after attempting to create the public mailbox member. This typically includes details about the newly created member or error information if the operation failed.
No binary data output is produced by this node.
Dependencies
- Requires an API authentication token, either via a Tenant Token credential or OAuth2 credential.
- Connects to the Lark Suite Open APIs at
https://open.larksuite.com/open-apis. - Proper configuration of credentials in n8n is necessary for successful API calls.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid credentials.
- Invalid Public Mailbox Id: Verify that the provided mailbox ID or address exists and is accessible.
- Missing required fields: The
Public Mailbox Idis mandatory; ensure it is provided. - Custom Body issues: If using a custom body, ensure the JSON structure matches the API expectations to avoid malformed request errors.
- API rate limits or permissions: Check that the API key or OAuth token has sufficient permissions to modify mailbox members.
Links and References
- Lark Suite Open API Documentation
- Managing Public Mailboxes in Lark Email (general reference)