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 node "Lark Calendar" provides integration with the Lark Suite calendar service, enabling users to manage calendar events programmatically. Specifically, the "Obtain Event List" operation under the "Event" resource allows users to retrieve a list of events from a specified calendar.
This node is beneficial in scenarios where automated workflows need to access calendar data, such as syncing events with other systems, generating reports on scheduled meetings, or triggering actions based on upcoming events.
For example, a user might use this node to fetch all events from a team calendar to send daily reminders or to integrate event data into a CRM system.
Properties
Name | Meaning |
---|---|
Authentication | Method of authenticating API requests. Options: Tenant Token, OAuth2. |
Calendar Id | The unique identifier of the calendar from which to obtain the event list. Required field. |
Options | Additional optional settings for the request. Currently supports: Use Custom Body (boolean) to specify if a custom request body should be used. |
Output
The node outputs JSON data representing the list of calendar events retrieved from the specified calendar. Each event typically includes details such as event ID, title, start and end times, attendees, and other metadata defined by the Lark Calendar API.
If binary data output is supported (not indicated here), it would represent attachments or related files associated with events, but this node primarily deals with JSON event data.
Dependencies
- Requires an active connection to the Lark Suite Open APIs.
- Needs either a Tenant Token or OAuth2 authentication credential configured in n8n.
- The base URL for API requests is
https://open.larksuite.com/open-apis
. - Proper permissions/scopes must be granted to the API credentials to read calendar events.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens will cause authorization errors.
- Incorrect or missing Calendar Id will result in failure to retrieve events.
- Network connectivity problems can prevent API calls from succeeding.
Error messages:
- Authorization errors usually indicate invalid credentials or insufficient permissions; verify and refresh tokens as needed.
- "Calendar not found" or similar errors suggest the provided Calendar Id is incorrect or inaccessible.
- API rate limits may cause temporary failures; consider implementing retry logic or checking quota usage.
Links and References
- Lark Suite Open API Documentation — For details on calendar-related IDs and event structures.
- Lark Calendar API Reference — Official API endpoints and parameters.