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.
Common scenarios where this node is useful include:
- Automating calendar management workflows by programmatically deleting outdated or canceled events.
- Synchronizing external systems with a CalDAV calendar by removing events that no longer apply.
- Cleaning up test or temporary events created during automated processes.
For example, you could use this node in a workflow triggered when a meeting is canceled in another system, automatically deleting the corresponding event from your CalDAV calendar.
Properties
| Name | Meaning |
|---|---|
| Calendar Name or ID | Select the calendar from which to delete the event. You can choose from a list of calendars or specify a calendar ID using an expression. This should be a server-relative path starting with "/". |
| Event ID | The unique identifier of the event to delete. This corresponds to the event's filename (without .ics) on the CalDAV server. |
Output
The node outputs JSON data containing:
success(boolean): Indicates whether the deletion was successful (true if HTTP status code is 2xx).statusCode(number): The HTTP status code returned by the CalDAV server for the delete request.eventId(string): The ID of the event that was requested to be deleted.calendarPath(string): The server-relative path of the calendar from which the event was deleted.
No binary data output is produced by this operation.
Example output JSON:
{
"success": true,
"statusCode": 204,
"eventId": "event-123",
"calendarPath": "/calendars/user/calendar/"
}
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 to interact with the CalDAV server.
- Proper permissions on the CalDAV server are required to delete events.
Troubleshooting
- Invalid Base URL: If the base URL in credentials is missing or does not start with
http://orhttps://, the node will throw an error. Ensure the URL includes the protocol and is correctly formatted. - Absolute URLs in Path Fields: Paths such as calendar paths or event IDs must be server-relative (start with
/). Absolute URLs are not allowed and will cause errors. - Host Not Found / Connection Refused: These errors indicate network issues or incorrect server hostname/port. Verify server accessibility and credentials.
- Timeouts: Network slowness or server unavailability can cause timeouts. Check network connectivity and server status.
- HTTP Errors: Non-success HTTP status codes (e.g., 403 Forbidden, 404 Not Found) may indicate permission issues or invalid event IDs. Confirm that the event exists and the user has rights to delete it.
If the node is set to continue on failure, errors will be included in the output for each item.