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

This node, named "Lark Calendar," is designed to manage calendar-related data within the Lark platform. It provides functionality to interact with Lark's calendar services, enabling users to automate tasks such as creating, updating, retrieving, or deleting calendar events and related information. This node is beneficial in scenarios where integration with Lark's calendar system is needed, for example:

Automatically scheduling meetings based on triggers from other apps.
Syncing calendar events between Lark and other calendar services.
Managing event details programmatically within workflows.

Properties

Name	Meaning
Authentication	Method of authenticating API requests. Options: "Tenant Token" (using a tenant-level token) or "OAuth2" (using OAuth2 authentication).
Options	Additional optional settings for the request.
- Use Custom Body	Boolean flag indicating whether to send a custom request body instead of the default one.

Output

The node outputs JSON data representing the response from the Lark Calendar API. The structure of this JSON depends on the specific calendar operation performed but generally includes details about calendar events or related entities. If binary data were involved (e.g., attachments), it would be included accordingly, but this node primarily deals with JSON responses.

Dependencies

Requires access to Lark's Open APIs at https://open.larksuite.com/open-apis.
Requires either a tenant token credential or an OAuth2 credential configured in n8n for authentication.
No additional external dependencies are indicated.

Troubleshooting

Authentication errors: Ensure that the correct authentication method is selected and that the corresponding credentials are valid and have sufficient permissions.
API request failures: Check network connectivity and verify that the base URL (https://open.larksuite.com/open-apis) is reachable.
Invalid custom body usage: If "Use Custom Body" is enabled, ensure the custom body format matches the expected API schema to avoid request errors.
Missing or incorrect properties: Verify that all required input properties are set correctly according to the operation being performed.