Lark Calendar

Lark Calendar Management

Actions32

Calendar Actions
Acl Actions
Event Actions
Event Attendee Actions
Event Attendee Chat Member Actions
- Obtain The List Of Members Of Group Invitees Of An Event
Freebusy Actions
- Query Availability
Timeoff Actions
- Create A Leave Event
- Delete A Leave Event
Setting Actions
- Generate Caldav Configuration
Exchange Binding Actions

Overview

The node enables creating a leave event (time off) in a calendar system, specifically for the "Timeoff" resource with the "Create A Leave Event" operation. It is useful for automating employee leave management by programmatically adding leave events to a user's calendar. For example, HR systems can integrate this node to automatically record approved leaves or absences without manual entry.

Properties

Name	Meaning
Authentication	Method of authentication to use: either "Tenant Token" or "OAuth2".
Description	Text description of the leave event.
End Time	The end time of the leave event (string format).
Start Time	The start time of the leave event (string format).
Timezone	Timezone identifier for the leave event times.
Title	Title or name of the leave event.
User Id	Identifier of the user for whom the leave event is created.
Custom Body	JSON object allowing full customization of the request body instead of using individual fields.
Options > Use Custom Body	Boolean flag to indicate whether to send the custom JSON body instead of standard fields.

Output

The node outputs JSON data representing the response from the calendar API after creating the leave event. This typically includes details about the newly created leave event such as its ID, status, and timestamps. There is no indication that binary data is output.

Dependencies

Requires an API key credential or OAuth2 token for authentication.
Connects to the Lark Suite Open APIs at https://open.larksuite.com/open-apis.
Proper configuration of credentials in n8n is necessary to authenticate requests.

Troubleshooting

Common issues:
- Invalid or expired authentication tokens will cause authorization errors.
- Incorrect date/time formats may lead to validation errors from the API.
- Missing required fields like user_id, start_time, or end_time can cause request failures.
Error messages:
- Authorization errors: Check that the API key or OAuth2 token is valid and has proper permissions.
- Validation errors: Ensure date/time strings are correctly formatted and timezone is valid.
- API errors: Review the custom body if used, to ensure it matches expected schema.