Lark Calendar icon

Lark Calendar

Lark Calendar Management

Actions32

Overview

This node, named "Lark Calendar," provides management capabilities for calendar-related resources within the Lark platform. Specifically, the "Exchange Binding" resource with the operation "Connect An Exchange Account" allows users to link an Exchange account to a Lark calendar user. This is useful in scenarios where organizations want to synchronize or integrate their Microsoft Exchange calendars with Lark's calendar system, enabling unified scheduling and event management across platforms.

Practical examples include:

  • Automatically connecting employees' Exchange accounts to their Lark calendars for seamless event synchronization.
  • Enabling administrators to manage calendar bindings centrally by specifying admin and user accounts.
  • Facilitating hybrid calendar environments where both Exchange and Lark calendars coexist.

Properties

Name Meaning
Authentication Method of authentication to use: either "Tenant Token" (an API key credential) or "OAuth2".
Admin Account The email or identifier of the administrator account responsible for managing the binding.
Exchange Account The email or identifier of the Exchange account to be connected.
User Id The identifier of the user in Lark to whom the Exchange account will be bound.
Custom Body A JSON object allowing the user to specify a custom request body instead of using predefined fields. Useful for advanced or non-standard requests.
Use Custom Body Boolean option to toggle between using the predefined input fields or sending a fully custom JSON body.

Output

The node outputs JSON data representing the response from the Lark API after attempting to connect the Exchange account. This typically includes confirmation of the binding status or error details if the operation failed.

No binary data output is involved.

Dependencies

  • Requires an active connection to the Lark Open API endpoint (https://open.larksuite.com/open-apis).
  • Requires authentication via either a Tenant Token credential or OAuth2 token configured in n8n.
  • No additional external dependencies beyond standard HTTP requests to the Lark API.

Troubleshooting

  • Common Issues:

    • Incorrect or missing authentication credentials will cause authorization failures.
    • Providing invalid or mismatched email/user IDs may result in errors from the API indicating that the user or account does not exist.
    • Using the custom body option incorrectly (e.g., malformed JSON) can lead to request failures.

  • Error Messages:

    • Authorization errors: Check that the correct authentication method is selected and credentials are valid.
    • Validation errors: Ensure all required fields (admin_account, exchange_account, user_id) are correctly filled unless using a custom body.
    • API errors: Review the response message for specific issues such as permission denied or account conflicts.

Links and References

Discussion