CalDAV icon

CalDAV

Interact with CalDAV servers to manage calendars, events, todos, and free/busy information
Join our community

Actions15

Overview

The node provides functionality to update calendar events on a CalDAV-compatible calendar server. It allows users to modify existing events by specifying the calendar URL, event unique identifier, and updated event details such as title, description, timing, location, attendees, and additional metadata like priority and recurrence rules.

This node is beneficial in scenarios where automated workflows need to keep calendar events synchronized or updated based on external triggers or data changes. For example, updating meeting times or details when a project deadline shifts, or modifying event attendees dynamically.

Properties

Name Meaning
Calendar URL The URL path of the calendar collection where the event resides (e.g., /calendars/user/personal/).
Event UID The unique identifier of the event to update.
Summary (Title) The title or summary of the event.
Description Detailed description of the event.
Start Date & Time When the event starts.
End Date & Time When the event ends.
All Day Event Whether this is an all-day event (true/false).
Location Event location or meeting room.
Attendees Comma-separated list of attendee email addresses.
Additional Fields Collection of optional fields:
- Priority Event priority level; options: High, Medium, Low.
- Status Event status; options: Confirmed, Tentative, Cancelled.
- Timezone Timezone for the event (default "UTC").
- Recurrence Rule RRULE string defining recurring event pattern (RFC 5545 format).
- Alarm (Minutes Before) Minutes before event start to trigger an alarm notification.

Output

The node outputs JSON data representing the updated event details after the operation completes successfully. This typically includes confirmation of the updated event properties as stored on the calendar server.

If the node supports binary data output (not evident from the provided code), it would relate to attachments or calendar files, but no such indication is present here.

Dependencies

  • Requires access to a CalDAV-compatible calendar server.
  • Needs valid authentication credentials (such as an API key or token) configured in n8n to authorize requests to the calendar server.
  • The calendarUrl must correctly point to the calendar collection on the server.
  • The event identified by eventUid must exist on the specified calendar.

Troubleshooting

  • Common Issues:

    • Incorrect or malformed calendarUrl leading to failure in locating the calendar.
    • Invalid or expired authentication credentials causing authorization errors.
    • Non-existent eventUid resulting in "event not found" errors.
    • Date/time values that are inconsistent (e.g., end time before start time).
    • Improperly formatted recurrence rules causing parsing errors.

  • Error Messages and Resolutions:

    • "Unauthorized" or "Authentication failed": Verify API credentials and permissions.
    • "Event not found": Check that the eventUid matches an existing event in the specified calendar.
    • "Invalid date/time" or similar: Ensure start and end times are valid and properly formatted.
    • "Malformed RRULE": Validate recurrence rule syntax against RFC 5545 standards.

Links and References

Discussion