Actions5
- Calendar Actions
Overview
This node integrates with CalDAV servers to manage calendar events. Specifically, the Delete Event operation allows users to remove an event from a specified calendar on a CalDAV-compatible server. This is useful for automating calendar management tasks such as cleaning up outdated or canceled events.
Practical examples include:
- Automatically deleting canceled meetings from a team calendar.
- Removing test or placeholder events after automated workflows complete.
- Syncing event deletions from other systems into a CalDAV calendar.
Properties
| Name | Meaning |
|---|---|
| Calendar Name or ID | Select the calendar from which to delete the event. Options are loaded dynamically from the CalDAV server or can be specified via expression. |
| Event ID | The unique identifier of the event to delete within the selected calendar. |
Output
The node outputs a JSON object containing:
success(boolean): Indicates whether the deletion was successful (HTTP status code 2xx).statusCode(number): The HTTP response status code returned by the CalDAV server.eventId(string): The ID of the event that was requested to be deleted.calendarPath(string): The path or ID of the calendar from which the event was deleted.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a CalDAV server with valid credentials including a base URL.
- The base URL must include the protocol (
http://orhttps://) and point to the CalDAV server endpoint. - The node uses HTTP methods like DELETE authenticated via the provided API key credential.
- Proper permissions on the CalDAV server are necessary to delete events.
Troubleshooting
- Invalid Base URL in credentials: Ensure the base URL includes the protocol and is correctly formatted without trailing slashes.
- Absolute URLs not allowed in path fields: Paths must be server-relative starting with
/. Do not use full URLs for calendar or event paths. - Host not found / Connection refused / Timeout errors: Check network connectivity, server hostname, port accessibility, and firewall settings.
- HTTP errors (non-2xx status codes): Verify that the event ID and calendar path are correct and that the user has permission to delete events.
- If the node throws errors about invalid URLs or encoding, ensure special characters in paths are properly encoded or use expressions to provide safe values.