Lark Email icon

Lark Email

Lark Email Management

Overview

This node manages public mailbox aliases within the Lark Email system. Specifically, the "Delete A Public Mailbox Alias" operation allows users to remove an alias associated with a public mailbox. This is useful in scenarios where an alias is no longer needed or should be revoked for security or organizational reasons.

Practical examples include:

  • Cleaning up outdated or unused email aliases linked to a shared mailbox.
  • Removing mistakenly created aliases to prevent misdirected emails.
  • Managing email routing by controlling which aliases are active.

Properties

Name Meaning
Authentication Method of authentication to use: either "Tenant Token" (an API key credential) or "OAuth2" (OAuth 2.0 token).
Public Mailbox Id The identifier or address of the public mailbox from which the alias will be deleted.
Alias Id The identifier of the specific alias to delete from the public mailbox.
Options > Use Custom Body Boolean flag indicating whether to send a custom request body instead of the default.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this includes confirmation of successful deletion or error details if the operation failed.

No binary data output is involved in this operation.

Dependencies

  • Requires access to the Lark Suite Open APIs at https://open.larksuite.com/open-apis.
  • Requires valid authentication credentials, either a tenant token or OAuth2 token configured in n8n.
  • The node expects proper permissions to manage public mailbox aliases via the Lark Email API.

Troubleshooting

  • Common Issues:

    • Invalid or expired authentication tokens can cause authorization failures.
    • Incorrect Public Mailbox Id or Alias Id may lead to "not found" errors.
    • Insufficient permissions on the API credentials might block alias deletion.
  • Error Messages and Resolutions:

    • 401 Unauthorized: Check that the authentication token is valid and has not expired.
    • 404 Not Found: Verify that the Public Mailbox Id and Alias Id are correct and exist.
    • 403 Forbidden: Ensure the API credentials have the necessary permissions to delete aliases.
    • 400 Bad Request: If using a custom body option, ensure the request body format matches API expectations.

Links and References

Discussion