Lark Calendar icon

Lark Calendar

Lark Calendar Management

Actions32

Overview

The node provides integration with Lark Calendar, specifically allowing management of calendar access control lists (ACLs). The "Create Access Control" operation enables users to add new ACL entries to a specified calendar. This is useful for scenarios where you want to programmatically grant specific roles or permissions to users or groups on a calendar, such as sharing calendar events with team members or external collaborators.

Practical examples include:

  • Automatically granting read or write access to a calendar when onboarding new employees.
  • Setting up calendar permissions based on project teams or departments.
  • Managing calendar sharing settings in bulk via workflows.

Properties

Name Meaning
Authentication Method of authenticating API requests. Options: Tenant Token, OAuth2.
Calendar Id The unique identifier of the calendar to which the ACL entry will be added.
Role The permission role to assign in the ACL entry (e.g., reader, writer).
Scope Defines the scope of the ACL entry, including type and user_id. For example, specifying a user or group to whom the role applies.
Custom Body A JSON object allowing full customization of the request body sent to the API, overriding standard properties if enabled.
Options > Use Custom Body Boolean flag to indicate whether to use the custom JSON body instead of the standard structured inputs.

Output

The node outputs JSON data representing the response from the Lark Calendar API after creating the ACL entry. This typically includes details about the newly created access control record, such as its ID, assigned role, and scope information.

If binary data were involved (not indicated here), it would represent file attachments or similar content, but this node focuses on JSON responses related to calendar ACL management.

Dependencies

  • Requires an API authentication credential, either a Tenant Token or OAuth2 token configured in n8n.
  • Connects to the Lark Suite Open APIs at https://open.larksuite.com/open-apis.
  • No additional external dependencies beyond the configured credentials and network access to Lark's API.

Troubleshooting

  • Common issues:
    • Invalid or expired authentication tokens will cause authorization errors.
    • Incorrect or missing Calendar Id can result in resource not found errors.
    • Improperly formatted scope or role values may lead to validation errors from the API.
  • Error messages:
    • 401 Unauthorized: Check that the API credentials are valid and have necessary permissions.
    • 404 Not Found: Verify the Calendar Id is correct and accessible by the authenticated user.
    • 400 Bad Request: Review the role and scope fields for correctness; ensure required fields are provided.
  • To resolve, confirm credentials, validate input parameters, and consult Lark API documentation for expected formats.

Links and References

Discussion