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 operation deletes a member from a specified public mailbox in the Lark Email system. It is useful for managing access control and membership of shared mailboxes, allowing administrators to remove users who should no longer have access.
Common scenarios:
- Removing former employees or collaborators from a shared public mailbox.
- Managing team mailbox memberships dynamically based on project changes.
- Automating cleanup of mailbox members as part of user lifecycle management.
Example:
An admin wants to revoke access for a user with ID 12345 from the public mailbox identified by team-support@company.com. Using this node operation, they provide the mailbox ID and member ID to delete that member's access.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" (an API key credential) or "OAuth2". |
| Public Mailbox Id | Unique identifier or email address of the public mailbox from which to remove a member. |
| Member Id | Unique identifier of the member to be deleted from the public mailbox. |
| Options | Additional options: • Use Custom Body (boolean) - whether to send a custom request body. |
Output
The node outputs JSON data representing the result of the deletion operation. Typically, this will include confirmation of success or details about any error encountered. The exact structure depends on the API response but generally confirms that the member was removed.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Lark Suite Open APIs.
- Must be configured with either:
- A valid Tenant Token credential (API key), or
- OAuth2 credentials authorized for mailbox management.
- Network access to
https://open.larksuite.com/open-apis.
Troubleshooting
- Invalid or missing authentication: Ensure that the selected authentication method is properly configured with valid credentials.
- Incorrect Public Mailbox Id or Member Id: Verify that the IDs provided correspond exactly to existing mailbox and member identifiers.
- Permission errors: The authenticated user must have sufficient rights to modify the public mailbox membership.
- API rate limits or network issues: Check connectivity and API usage quotas if requests fail unexpectedly.
- Using Custom Body option: If enabled, ensure the custom body format matches API expectations; otherwise, the request may be rejected.