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 "Lark Calendar" provides management capabilities for Lark Calendar services. Specifically, the "Generate Caldav Configuration" operation under the "Setting" resource allows users to generate configuration details required for CalDAV synchronization with a device. This is useful when integrating Lark Calendar with external calendar clients that support CalDAV protocol, enabling seamless calendar syncing.

Typical use cases include:

Automatically generating CalDAV configuration for a new device to sync calendars.
Integrating Lark Calendar with third-party calendar applications that require CalDAV setup.
Managing device-specific calendar access configurations programmatically.

Properties

Name	Meaning
Authentication	Method of authentication to use: either "Tenant Token" or "OAuth2".
Device Name	The name of the device for which the CalDAV configuration is being generated.
Use Custom Body	Boolean flag indicating whether to send a custom JSON body instead of the default structure.
Custom Body	A JSON object representing a custom request body to send if "Use Custom Body" is enabled.

Output

The node outputs JSON data containing the CalDAV configuration details generated by the Lark Calendar API. This typically includes URLs, tokens, or other necessary parameters required to configure CalDAV on the specified device.

No binary data output is indicated in the source code.

Dependencies

Requires an API key credential for authentication, either via a tenant token or OAuth2.
Connects to the Lark Suite Open APIs at https://open.larksuite.com/open-apis.
Proper credentials must be configured in n8n for authentication to succeed.

Troubleshooting

Authentication errors: Ensure that the correct authentication method is selected and valid credentials are provided.
Invalid device name: The device name should be a non-empty string; otherwise, the API may reject the request.
Custom body issues: If using a custom body, ensure the JSON is well-formed and matches the expected API schema.
API connectivity: Verify network access to the Lark Suite API endpoint and that the base URL has not changed.