Overview
This node allows updating an existing calendar event using the CalDAV protocol. It is useful for scenarios where you need to modify details of a previously created event, such as changing its time, location, attendees, or other metadata. For example, you might use this node to update a meeting's start and end times, add new attendees, or change the event description after it has been initially scheduled.
Properties
| Name | Meaning |
|---|---|
| Event Summary | Title of the calendar event. |
| Event Start | Start date and time of the event. |
| Event End | End date and time of the event. |
| Duration | Duration of the event in iCalendar format (e.g., "P1D" for 1 day, "PT1H30M" for 1 hour and 30 minutes). Ignored if Event End is provided. |
| Location | Location of the event. |
| Description | Description of the event. |
| Existing Event | The existing event object to update, typically obtained from a previous fetch operation. This is required to identify which event to update. |
| Options | Collection of optional settings including: |
| - Alarms | List of alarms/reminders for the event. Each alarm can specify an action (Display, Email, Audio), trigger time, and description. |
| - Attendees | List of people attending the event, each with name, email, and role (Required, Optional, Chair, Non-Participant). |
| - Categories | Comma-separated list of iCalendar categories for the event. |
| - Class | Visibility of the event when published: Public, Private, or Confidential. |
| - Comment | Additional comment or note about the event. |
| - Exception Dates | Comma-separated list of dates to exclude from a recurring event. |
| - Extra Properties | Custom properties added to the iCalendar event as non-standard fields. |
| - Full Day | Boolean indicating whether the event lasts the entire day. |
| - Geo Location | Geographic coordinates for the event location (e.g., "52.51977, 13.40590"). |
| - Organizer | Information about the event organizer, including name and email. |
| - Priority | Priority level of the event (High=1, Medium=5, Low=9). |
| - Recurrence Rule | RRULE string defining recurrence pattern (e.g., "FREQ=WEEKLY;BYDAY=MO,WE,FR"). |
| - Status | Status of the event: Confirmed, Tentative, or Cancelled. |
| - Transparency | Whether the event blocks time on the calendar: Opaque (blocks time) or Transparent (does not block time). |
| - URL | URL associated with the event. Must be a valid URL format. |
Output
The node outputs the updated event data in JSON format. This includes all the properties of the event after the update, reflecting any changes made during execution. If the event contains binary data (such as attachments), those would be included accordingly, but this node primarily deals with JSON event data.
Dependencies
- Requires access to a CalDAV server with appropriate credentials (an API key or authentication token).
- The node depends on the CalDAV protocol implementation to communicate with the calendar service.
- Proper configuration of credentials within n8n is necessary to authenticate requests.
Troubleshooting
Common Issues:
- Providing an invalid or incomplete existing event object will cause the update to fail.
- Incorrect date/time formats for start, end, or duration may result in errors.
- Missing required fields like the existing event or organizer email can cause validation failures.
- Network or authentication issues with the CalDAV server will prevent successful updates.
Error Messages:
- Errors related to authentication usually indicate misconfigured credentials or expired tokens.
- Validation errors often mention missing required properties or invalid formats.
- Server errors may indicate issues on the CalDAV service side or unsupported features.
Resolutions:
- Ensure the existing event object is correctly fetched and passed to the update operation.
- Validate date/time inputs conform to ISO 8601 or iCalendar standards.
- Verify credentials and network connectivity to the CalDAV server.
- Review error messages for specific property issues and correct input accordingly.