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 "Lark Email" node provides integration with Lark's email management API. It is designed to facilitate operations related to managing emails within the Lark platform, such as sending or manipulating email data. This node is useful in automation workflows where email communication through Lark needs to be automated or integrated with other systems.
Common scenarios include:
- Sending emails automatically based on triggers from other apps.
- Managing email content or metadata programmatically.
- Integrating Lark email functionality into broader business processes.
Practical example:
- Automatically send a notification email via Lark when a new support ticket is created in a helpdesk system.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with Lark API. Options: "Tenant Token" or "OAuth2". |
| Options | Additional options for the request. |
| - Use Custom Body | Boolean flag indicating whether to use a custom request body instead of default format. |
Output
The node outputs JSON data representing the response from the Lark email API. This typically includes information about the success or failure of the email operation performed, such as message IDs, status codes, or error messages.
If binary data is returned (not indicated here), it would represent attachments or raw email content, but this node primarily deals with JSON responses.
Dependencies
- Requires an API authentication token for Lark, either via a Tenant Token or OAuth2 credentials.
- The node communicates with the Lark Open API endpoint at
https://open.larksuite.com/open-apis. - Proper configuration of credentials in n8n is necessary to authenticate requests.
Troubleshooting
- Authentication errors: Ensure that the correct authentication method is selected and that the provided credentials are valid and have sufficient permissions.
- API request failures: Check network connectivity and verify that the Lark API service is operational.
- Invalid custom body: If using the "Use Custom Body" option, ensure the JSON structure matches the expected API schema to avoid request errors.
- Missing required properties: Make sure all mandatory fields for the specific email operation are set correctly.