Actions5
- Calendar Actions
Overview
The CalDAV node enables interaction with CalDAV servers to manage calendar data programmatically. Specifically, the Update Event operation allows users to update an existing calendar event by providing its unique identifier and new event data in iCalendar (.ics) format.
This node is beneficial for automating calendar management tasks such as synchronizing events from other systems, updating meeting details, or modifying reminders without manual intervention.
Practical example:
A user can automate updating a recurring meeting's time or description across multiple calendars by feeding updated iCalendar data into this node, ensuring all participants see the latest event information.
Properties
| Name | Meaning |
|---|---|
| Calendar Name or ID | Select a calendar from the list or specify its server-relative path (e.g., /calendars/user/calendar/). This identifies which calendar contains the event to update. |
| Event ID | The unique identifier of the event to update within the selected calendar (e.g., event-123). |
| Event Data (iCalendar) | The updated event details formatted as an iCalendar (.ics) string. This replaces the existing event data. |
Output
The node outputs a JSON object containing:
success(boolean): Indicates whether the update operation was successful (HTTP status code 2xx).statusCode(number): The HTTP response status code returned by the CalDAV server.eventId(string): The identifier of the updated event.calendarPath(string): The server-relative path of the calendar where the event was updated.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a CalDAV-compatible server with valid credentials including a base URL.
- The base URL must include the protocol (
http://orhttps://) and be correctly configured in the node credentials. - The node uses HTTP methods like PUT with appropriate headers (
Content-Type: text/calendar,If-Match: *) to perform updates. - Proper permissions on the CalDAV server are necessary to modify events.
Troubleshooting
Invalid Base URL error:
Occurs if the base URL in credentials is missing or does not start withhttp://orhttps://.
Resolution: Ensure the base URL includes the protocol and is correctly set.Absolute URLs not allowed in path fields:
If the calendar path or event path is provided as a full URL instead of a server-relative path starting with/.
Resolution: Use server-relative paths only.Connection errors (ENOTFOUND, ECONNREFUSED, ETIMEDOUT):
Indicate network issues, unreachable server, or incorrect hostname/port.
Resolution: Verify network connectivity, server address, and firewall settings.HTTP errors (non-2xx status codes):
May indicate permission issues, invalid event IDs, or malformed iCalendar data.
Resolution: Check event existence, validate iCalendar format, and ensure proper access rights.If-Match header usage:
The update usesIf-Match: *header to overwrite any existing version of the event. If the server requires specific ETag values, updates may fail.
Resolution: Confirm server requirements for concurrency control.
Links and References
- CalDAV Protocol Specification (RFC 4791)
- iCalendar Format Specification (RFC 5545)
- n8n Expressions Documentation (for dynamic property values)