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 "Delete A Calendar" operation in the Lark Calendar node allows users to remove a specific calendar by its unique identifier. This is useful for managing calendars programmatically, such as cleaning up unused or obsolete calendars within an organization or personal workspace. For example, an admin might automate the deletion of project-specific calendars once a project concludes, ensuring the calendar list remains relevant and uncluttered.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: Tenant Token, OAuth2. |
| Calendar Id | The unique identifier of the calendar to be deleted. Required to specify which calendar should be removed. |
| Options | Additional optional settings. Currently supports: Use Custom Body (boolean) - whether to send a custom request body instead of the default format. |
Output
The output JSON typically contains the response from the Lark Calendar API after attempting to delete the specified calendar. This usually includes status information indicating success or failure of the deletion operation. There is no binary data output associated with this operation.
Dependencies
- Requires valid authentication credentials via either a Tenant Token or OAuth2 token.
- Depends on access to the Lark Suite Open APIs endpoint at
https://open.larksuite.com/open-apis. - Proper configuration of authentication credentials in n8n is necessary for successful API calls.
Troubleshooting
- Invalid Calendar Id: If the provided calendar ID does not exist or is malformed, the API will return an error. Verify the calendar ID against the official documentation or retrieve it dynamically before deletion.
- Authentication Errors: Using incorrect or expired tokens will cause authentication failures. Ensure that the selected authentication method is correctly configured and tokens are valid.
- Permission Issues: The authenticated user or token must have sufficient permissions to delete calendars. Lack of proper authorization will result in permission denied errors.
- Use Custom Body Option: Enabling this without providing a correct custom body may lead to malformed requests. Only enable if you intend to customize the request payload.
Links and References
- Lark Calendar API Documentation - Calendar-related IDs (for details on Calendar IDs)
- Lark Suite Open APIs Overview