Lark Calendar icon

Lark Calendar

Lark Calendar Management

Actions32

Overview

The node provides functionality to manage calendar time off events within the Lark Calendar system. Specifically, the "Delete A Leave Event" operation allows users to remove a previously created time off (leave) event by specifying its unique identifier. This is useful in scenarios where an employee's leave request needs to be canceled or corrected after submission.

Practical examples include:

  • Automatically deleting a leave event when a cancellation request is received from an HR system.
  • Cleaning up test or erroneous leave events during data synchronization processes.

Properties

Name Meaning
Authentication Method of authenticating API requests. Options: Tenant Token, OAuth2.
Timeoff Event Id The unique identifier of the time off application (leave event) to delete. This ID must correspond to an existing leave event in the calendar.
Options > Use Custom Body Whether to send a custom request body with the delete operation. Defaults to false (standard request).

Output

The output JSON typically contains the response from the Lark Calendar API confirming the deletion of the specified leave event. It may include status information or confirmation messages indicating success or failure of the deletion.

No binary data output is expected for this operation.

Dependencies

  • Requires access to the Lark Suite Open APIs for calendar management.
  • Requires either a Tenant Token or OAuth2 authentication credential configured in n8n to authorize API requests.
  • The base URL for API requests is https://open.larksuite.com/open-apis.

Troubleshooting

  • Invalid or missing Timeoff Event Id: If the provided event ID does not exist or is malformed, the API will return an error. Ensure the ID is correct and corresponds to an existing leave event.
  • Authentication errors: Using incorrect or expired credentials will cause authorization failures. Verify that the Tenant Token or OAuth2 token is valid and has necessary permissions.
  • API rate limits or network issues: Temporary failures might occur due to rate limiting or connectivity problems. Retrying after some time or checking network settings can help.
  • Use Custom Body option misuse: Enabling the custom body option without providing a proper body format may lead to request errors. Only enable if you intend to customize the request payload.

Links and References

Discussion