Lark Calendar icon

Lark Calendar

Lark Calendar Management

Actions32

Overview

The "Lark Calendar" node enables interaction with the Lark Calendar service, specifically allowing users to manage calendar-related data within their workflows. The "Obtain Calendar List" operation fetches a list of calendars accessible to the authenticated user or tenant. This is useful for scenarios where you want to display available calendars, synchronize events, or select a calendar for further operations such as event creation or updates.

Practical examples include:

  • Automatically retrieving all calendars for a user to present options in a UI.
  • Syncing calendar lists between Lark and another calendar system.
  • Filtering or processing events based on specific calendars retrieved dynamically.

Properties

Name Meaning
Authentication Method used to authenticate API requests. Options: "Tenant Token" or "OAuth2".
Options Additional optional settings for the request.
└─ Use Custom Body Boolean flag indicating whether to send a custom request body instead of default behavior.

Output

The node outputs JSON data containing the list of calendars retrieved from the Lark Calendar API. Each item in the output typically represents a calendar with its associated metadata such as calendar ID, name, description, and other relevant details provided by the API.

If binary data were involved (not indicated here), it would represent attachments or files related to calendar events, but this operation focuses solely on JSON calendar list data.

Dependencies

  • Requires an active connection to the Lark Suite API.
  • 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 credentials to access calendar information.

Troubleshooting

  • Authentication errors: Ensure that the selected authentication method is correctly configured and valid. Expired tokens or insufficient permissions will cause failures.
  • Empty calendar list: Verify that the authenticated user or tenant actually has calendars available. Also check if any filters or custom body options are restricting results.
  • API rate limits or connectivity issues: Network problems or hitting API limits may cause errors; retry after some time or check network settings.
  • Invalid custom body usage: If "Use Custom Body" is enabled, ensure the custom payload is correctly formatted according to the API specification to avoid request errors.

Links and References

Discussion