Actions15
Overview
This node allows users to create calendar events on a CalDAV-compatible calendar server by specifying event details such as title, description, timing, location, attendees, and additional options like priority and recurrence. It is useful for automating calendar management tasks, such as scheduling meetings, reminders, or recurring events directly from workflows without manual entry.
Practical examples include:
- Automatically creating team meeting events when a new project task is assigned.
- Scheduling recurring weekly sync meetings with predefined attendees.
- Setting alarms for important deadlines or appointments.
Properties
| Name | Meaning |
|---|---|
| Calendar URL | The URL path of the calendar collection where the event will be created (e.g., /calendars/user@example.com/personal/). |
| Summary (Title) | The title or summary of the event (e.g., "Team Meeting"). |
| Description | Detailed description of the event content or agenda. |
| Start Date & Time | The starting date and time of the event. |
| End Date & Time | The ending date and time of the event. |
| All Day Event | Whether the event lasts all day (true/false). |
| Location | Physical or virtual location of the event (e.g., "Conference Room A, 123 Main St"). |
| Attendees | Comma-separated list of attendee email addresses. |
| Additional Fields | Collection of optional fields: |
| - Priority | Event priority level; options are High (1), Medium (5), Low (9). |
| - Status | Event status; options are Confirmed, Tentative, Cancelled. |
| - Timezone | Timezone identifier for the event (default "UTC", e.g., "Europe/Berlin"). |
| - Recurrence Rule | RRULE string defining recurrence pattern according to RFC 5545 (e.g., FREQ=WEEKLY;BYDAY=MO,WE,FR). |
| - Alarm (Minutes Before) | Number of minutes before the event start time to trigger an alarm/reminder. |
Output
The node outputs JSON data representing the created event's details as returned by the CalDAV server. This typically includes confirmation of the event creation along with its unique identifier and properties. If binary data were involved (e.g., attachments), it would be summarized accordingly, but this node focuses on event metadata only.
Dependencies
- Requires access to a CalDAV-compatible calendar server.
- Needs appropriate API credentials or authentication tokens configured in n8n to authorize requests to the calendar server.
- The user must provide the correct calendar URL path corresponding to their calendar collection.
Troubleshooting
- Invalid Calendar URL: Ensure the calendar URL path is correct and accessible on the CalDAV server.
- Authentication Errors: Verify that the API key or authentication token is valid and has sufficient permissions to create events.
- Date/Time Issues: Make sure start and end times are valid and the end time is after the start time.
- Recurrence Rule Format: If using recurrence, ensure the RRULE string complies with RFC 5545 syntax.
- Attendee Format: Attendee emails should be comma-separated and valid email addresses.
- Common error messages usually relate to authorization failures, invalid input formats, or server connectivity issues. Checking credentials and input values typically resolves these.