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 enables management of Lark Email mailing list aliases, specifically allowing users to delete a mailing list alias. It is useful in scenarios where an organization needs to remove outdated or incorrect email aliases associated with a mailing list to maintain accurate communication channels.
For example, if a company has a mailing list for "[email protected]" and an alias "[email protected]" that is no longer valid, this node can be used to delete the alias to prevent emails from being sent to an obsolete address.
Properties
Name | Meaning |
---|---|
Authentication | Method of authentication to use: either "Tenant Token" or "OAuth2". |
Mailgroup Id | The unique ID or email address of the mailing list from which the alias will be deleted. |
Alias Id | The email address of the mailing list alias to delete. |
Options | Additional options; currently supports: |
- Use Custom Body | Whether to send a custom request body (boolean). |
Output
The node outputs JSON data representing the response from the Lark API after attempting to delete the mailing list alias. This typically includes status information indicating success or failure of the deletion operation.
No binary data output is involved.
Dependencies
- Requires access to the Lark Suite Open API endpoint at
https://open.larksuite.com/open-apis
. - Requires authentication via either:
- A Tenant Token credential.
- An OAuth2 credential.
- Proper configuration of these credentials within n8n is necessary for successful API calls.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens may cause authorization failures.
- Incorrect Mailgroup Id or Alias Id values will result in errors indicating the resource was not found.
- Network connectivity issues can prevent reaching the Lark API endpoint.
Error Messages:
- Authorization errors suggest checking and refreshing the provided credentials.
- "Not Found" errors indicate verifying the correctness of the mailing list and alias identifiers.
- API rate limits or quota exceeded errors require waiting or adjusting usage patterns.