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
This node, named "Lark Calendar," manages calendar-related operations within the Lark platform. Specifically, for the Exchange Binding resource and the Disconnect An Exchange Account operation, it allows users to disconnect an existing connection between a Lark calendar and an external Exchange account. This is useful when you want to revoke or terminate synchronization or integration with an Exchange calendar.
Practical scenarios include:
- Removing access to an Exchange calendar that is no longer needed.
- Cleaning up stale or invalid Exchange connections.
- Managing calendar integrations programmatically as part of automation workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: "Tenant Token" or "OAuth2". |
| Exchange Binding Id | The unique identifier of the Exchange connection to be disconnected. Required to specify which Exchange account binding to remove. |
| Options | Additional optional settings. Currently supports: - Use Custom Body (boolean): Whether to send a custom request body instead of the default. |
Output
The node outputs JSON data representing the result of the disconnect operation. Typically, this will confirm whether the disconnection was successful or provide error details if it failed.
If the node supports binary data output, it would relate to any files or attachments returned by the API, but in this case, the operation is about disconnecting an account and thus does not produce binary output.
Dependencies
- Requires an active API authentication credential, either via 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 are indicated.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens can cause authorization failures.
- Providing an incorrect or non-existent Exchange Binding Id will result in errors indicating the binding could not be found.
- Network connectivity issues may prevent reaching the Lark API endpoint.
Error messages:
- Authorization errors: Check that the selected authentication method is correctly configured and valid.
- Not found errors: Verify the Exchange Binding Id is correct and exists.
- Bad request errors: If using the "Use Custom Body" option, ensure the custom body format matches API expectations.
Links and References
- Lark Suite Open API Documentation
- Calendar-related IDs Explanation (for understanding Exchange Binding Id)