Actions32
- Calendar Actions
- Acl Actions
- Event Actions
- Event Attendee Actions
- Event Attendee Chat Member Actions
- Freebusy Actions
- Timeoff Actions
- Setting Actions
- Exchange Binding Actions
Overview
The "Lark Calendar" node enables interaction with the Lark Calendar service, specifically allowing users to obtain detailed information about a particular calendar by its ID. This node is useful in scenarios where automation workflows need to retrieve calendar metadata or details for scheduling, synchronization, or display purposes. For example, it can be used to fetch calendar details before creating events or to verify calendar properties within an automated process.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: "Tenant Token" (using a tenant-level API token) or "OAuth2" (user OAuth2 flow). |
| Calendar Id | The unique identifier of the calendar to obtain. Required to specify which calendar's details to retrieve. |
| Options | Additional optional settings: • Use Custom Body: Whether to send a custom request body instead of the default one. |
Output
The node outputs JSON data containing the details of the specified calendar. This typically includes metadata such as the calendar's name, description, owner, time zone, and other relevant attributes provided by the Lark Calendar API. The output does not include binary data.
Dependencies
- Requires access to the Lark Suite Open APIs.
- Needs either a Tenant Token credential or OAuth2 authentication configured in n8n to authorize API requests.
- The base URL for API requests is
https://open.larksuite.com/open-apis.
Troubleshooting
- Missing or invalid Calendar Id: Ensure that the Calendar Id property is correctly set and corresponds to an existing calendar accessible by the authenticated user or tenant.
- Authentication errors: Verify that the selected authentication method is properly configured with valid credentials or tokens.
- API rate limits or permission issues: Check that the API credentials have sufficient permissions to read calendar data and that usage limits are not exceeded.
- Custom Body option misuse: If "Use Custom Body" is enabled without providing a proper body, the request may fail. Use this option only if you intend to customize the request payload.
Links and References
- Lark Calendar API Documentation (for Calendar-related IDs and API details)
- Lark Suite Developer Portal