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 provides functionality to manage Lark Calendar resources, specifically focusing on Access Control List (ACL) entries. The "Delete Access Control" operation allows users to remove a specific ACL entry from a calendar, effectively revoking access permissions previously granted.
This node is beneficial in scenarios where calendar sharing needs to be updated or restricted dynamically, such as automating the removal of user access when they leave a team or project. For example, an organization can automate cleaning up calendar permissions after project completion to maintain security and privacy.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used for authenticating API requests. Options: Tenant Token, OAuth2. |
| Calendar Id | The unique identifier of the calendar from which the ACL entry will be deleted. Refer to Lark's documentation for details on calendar IDs. |
| Acl Id | The unique identifier of the ACL entry to delete. This specifies which access control record to remove. |
| Options | Additional optional settings. Currently supports: Use Custom Body (boolean) - whether to send a custom request body instead of the default format. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of successful deletion or error information if the operation failed. There is no binary data output associated with this operation.
Dependencies
- Requires authentication via either a Tenant Token or OAuth2 credentials.
- Connects to the Lark Suite Open APIs at
https://open.larksuite.com/open-apis. - Proper configuration of credentials within n8n is necessary to authorize API calls.
Troubleshooting
Common Issues:
- Invalid or expired authentication tokens may cause authorization failures.
- Incorrect Calendar Id or Acl Id values will result in errors indicating resource not found.
- Network connectivity issues can prevent API communication.
Error Messages:
- 401 Unauthorized: Check that the provided authentication token is valid and has sufficient permissions.
- 404 Not Found: Verify that the Calendar Id and Acl Id are correct and exist.
- 400 Bad Request: If using the custom body option, ensure the request body is correctly formatted according to API specifications.
Links and References
- Lark Calendar API Documentation — Details on Calendar-related IDs and ACL management.
- Lark Suite Developer Portal — General developer resources and API references.