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 enables subscribing to changes in calendar access control lists (ACLs) within the Lark Calendar service. It is useful for scenarios where you want to monitor and react to updates in who has access to a specific calendar, such as syncing permissions with another system, triggering notifications when access changes, or auditing calendar sharing activities.
For example, an organization might use this node to automatically update internal records whenever someone is granted or revoked access to a shared team calendar.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: "Tenant Token" or "OAuth2". |
| Calendar Id | The unique identifier of the calendar to monitor for ACL changes. |
| Use Custom Body | Boolean flag indicating whether to send a custom JSON body in the subscription request instead of the default structure. |
| Custom Body | A JSON object representing a custom request body to send if "Use Custom Body" is enabled. |
Output
The node outputs JSON data representing the response from the Lark Calendar API regarding the subscription to ACL changes. This typically includes confirmation details about the subscription status and any relevant metadata returned by the API.
No binary data output is indicated.
Dependencies
- Requires authentication via either a Tenant Token or OAuth2 credentials configured in n8n.
- Connects to the Lark Suite Open APIs at
https://open.larksuite.com/open-apis. - No additional external dependencies beyond the configured API credentials.
Troubleshooting
- Invalid Calendar ID: If the provided calendar ID is incorrect or does not exist, the API will likely return an error. Verify the calendar ID format and existence.
- Authentication Errors: Using invalid or expired credentials will cause authentication failures. Ensure that the Tenant Token or OAuth2 token is valid and has sufficient permissions.
- Custom Body Issues: When using a custom body, malformed JSON or missing required fields may cause the API to reject the request. Validate the JSON syntax and required parameters.
- Network or API Availability: Temporary network issues or API downtime can cause request failures. Retry after some time or check the Lark API status.
Links and References
- Lark Calendar API Documentation (for Calendar-related IDs and ACL management)
- Calendar-related IDs Explanation