Overview
This node allows you to create calendar events using the CalDAV protocol. It is useful for automating event creation in calendars that support CalDAV, such as personal or corporate calendars. Typical use cases include scheduling meetings, reminders, or any time-based appointments programmatically.
For example, you can create an event titled "Team Meeting" starting at a specific date and time, optionally specifying attendees, location, alarms, and recurrence rules. This helps integrate calendar management into workflows like CRM systems, project management tools, or notification services.
Properties
| Name | Meaning |
|---|---|
| Calendar Name | The name of the calendar where the event will be created. |
| Event Summary | Title or summary of the calendar event. |
| Event Start | Start date and time of the event. |
| Event End | End date and time of the event. If not provided, Duration can be used instead. |
| Duration | Duration of the event in iCalendar format (e.g., "P1D" for 1 day, "PT1H30M" for 1 hour 30 minutes). Ignored if Event End is specified. |
| Location | Location where the event takes place. |
| Description | Detailed description of the event. |
| Options | Collection of additional optional settings: |
| - Alarms | One or more alarms/reminders for the event. Each alarm has: Action (Display, Email, Audio), Trigger time (relative or absolute), and Description. |
| - Attendees | List of people attending the event. Each attendee includes Name, Email, and Role (Required, Optional, Chair, Non-Participant). |
| - Categories | Comma-separated list of categories/tags for the event. |
| - Class | Visibility of the event when published: Public, Private, or Confidential. |
| - Comment | Additional comments or notes about the event. |
| - Exception Dates | Comma-separated dates to exclude from recurring events. |
| - Extra Properties | Custom non-standard properties added to the event, with name-value pairs. |
| - Full Day | Boolean indicating if the event lasts the entire day. |
| - Geo Location | Geographic coordinates (latitude, longitude) 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 from 1 (high) to 9 (low). Default is medium (5). |
| - Recurrence Rule | RRULE string defining how the event recurs (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). |
| - URL | URL associated with the event, validated as a proper URL. |
Output
The node outputs JSON data representing the created calendar event. This typically includes all event details as stored in the calendar system, such as event ID, timestamps, attendees, alarms, and other metadata.
If the calendar supports binary attachments or files related to the event, those would be handled separately, but this node primarily focuses on event data in JSON format.
Dependencies
- Requires access to a CalDAV-compatible calendar server.
- Needs an API authentication token or API key credential configured in n8n to authenticate requests to the CalDAV service.
- The node depends on internal routing logic and resource definitions for calendar and event operations bundled within the node's codebase.
Troubleshooting
- Authentication errors: Ensure the API key or authentication token is correctly configured and has sufficient permissions to create events.
- Invalid date/time formats: Provide valid ISO 8601 date-time strings for start and end times. Incorrect formats may cause failures.
- Missing required fields: Calendar Name, Event Summary, and Event Start are mandatory. Omitting these will result in errors.
- Recurrence rule syntax errors: RRULE strings must follow iCalendar specification. Invalid rules may cause the event creation to fail.
- Network issues: Connectivity problems with the CalDAV server will prevent event creation.
- Permission denied: The authenticated user must have write access to the specified calendar.