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 functionality to manage Lark email resources, specifically here focusing on creating a public mailbox alias. This operation allows users to add an alias email address to an existing public mailbox in Lark's email system. Such a feature is useful for organizations that want to create alternative or easier-to-remember email addresses pointing to the same public mailbox, facilitating better email management and routing.
Practical examples include:
- Creating department-specific aliases (e.g., [email protected]) that forward to a shared public mailbox.
- Adding temporary aliases for events or campaigns without creating new mailboxes.
- Simplifying email addresses for external communication while maintaining centralized mailbox management.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" or "OAuth2". |
| Public Mailbox Id | The identifier or email address of the public mailbox to which the alias will be added. |
| Email Alias | The alias email address to create for the public mailbox. |
| Custom Body | A JSON object allowing the user to specify a custom request body instead of the default one. |
| Options > Use Custom Body | Boolean flag indicating whether to send a custom JSON body instead of the standard fields. |
Output
The node outputs JSON data representing the response from the Lark API after attempting to create the public mailbox alias. This typically includes confirmation details such as the created alias information or error messages if the creation failed.
If binary data were involved (not indicated here), it would represent attachments or files related to the mailbox alias, but this node focuses solely on JSON responses.
Dependencies
- Requires access to Lark Suite's Open APIs at
https://open.larksuite.com/open-apis. - Needs valid authentication credentials, either via a Tenant Token or OAuth2 token.
- Proper configuration of these credentials within n8n is necessary for successful API calls.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect or non-existent public mailbox IDs causing resource not found errors.
- Malformed email alias strings resulting in validation errors from the API.
- Using a custom body with incorrect JSON structure may cause request failures.
Error Messages & Resolutions:
- 401 Unauthorized: Check that the provided authentication token is valid and has not expired.
- 404 Not Found: Verify the public mailbox ID or address exists and is correctly specified.
- 400 Bad Request: Ensure the email alias format is correct and matches expected patterns.
- Invalid JSON Body: When using the custom body option, validate the JSON syntax before sending.