Lark Email icon

Lark Email

Lark Email Management

Overview

The "Create A Public Mailbox" operation in the Lark Email node allows users to create a new public mailbox within the Lark Suite environment. This is useful for organizations that want to set up shared email addresses accessible by multiple team members, such as [email protected] or [email protected].

Common scenarios include:

  • Setting up departmental mailboxes for customer support or sales.
  • Creating generic contact emails that multiple users can monitor and respond from.
  • Automating the creation of public mailboxes during onboarding or system setup.

Practical example: An admin automates creating a public mailbox named "Support Team" with the email [email protected] so that all support staff can access incoming messages.

Properties

Name Meaning
Authentication Method of authenticating API requests. Options: Tenant Token, OAuth2
Email The email address for the new public mailbox (e.g., [email protected])
Name The display name for the public mailbox (e.g., "Support Team")
Use Custom Body Boolean flag to indicate whether to send a custom JSON body instead of using Email and Name properties
Custom Body JSON object representing a custom request body to send when creating the mailbox. Should include at least email and name fields if used

Output

The node outputs JSON data representing the response from the Lark Suite API after attempting to create the public mailbox. This typically includes details about the created mailbox such as its ID, email, name, and status.

If the operation fails, the output will contain error information returned by the API.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to Lark Suite's Open APIs.
  • Needs either a Tenant Token credential or OAuth2 authentication configured in n8n.
  • The base URL for API requests is https://open.larksuite.com/open-apis.
  • Proper permissions/scopes must be granted to the API credentials to create public mailboxes.

Troubleshooting

  • Invalid Authentication: Errors related to authentication usually mean the provided token or OAuth2 credentials are invalid or expired. Refresh or reconfigure credentials.
  • Missing Required Fields: Ensure both email and name are provided unless using a fully custom JSON body.
  • API Rate Limits: If you receive rate limit errors, reduce request frequency or check Lark Suite API usage policies.
  • Permission Denied: The authenticated user may lack permission to create public mailboxes. Verify API scopes and user roles.
  • Malformed Custom Body: When using the custom body option, ensure the JSON is valid and contains all required fields.

Links and References

Discussion