Actions5
- Calendar Actions
Overview
This node integrates with CalDAV servers to manage calendar events. Specifically, the Create Event operation allows users to add new events to a specified calendar on a CalDAV-compatible server by uploading event data in iCalendar (.ics) format.
Common scenarios where this node is beneficial include:
- Automating event creation in corporate or personal calendars hosted on CalDAV servers.
- Synchronizing events from other systems into a CalDAV calendar.
- Programmatically managing calendar entries without manual interaction with calendar apps.
For example, you could use this node to create meeting invites automatically when a new project task is created, or to log appointments from an external booking system into your CalDAV calendar.
Properties
| Name | Meaning |
|---|---|
| Calendar Name or ID | Select the target calendar from a list of available calendars fetched from the CalDAV server, or specify its path manually (server-relative path starting with "/"). |
| Event ID | A unique identifier string for the event to be created. This will be used as the filename (with .ics extension) on the server. |
| Event Data (iCalendar) | The full event details formatted in iCalendar (.ics) format. This string contains all event information such as start/end time, summary, description, attendees, etc. |
Output
The node outputs a JSON object with the following fields:
success: Boolean indicating whether the event creation was successful (HTTP status code 2xx).statusCode: The HTTP response status code returned by the CalDAV server.eventId: The event identifier used in the request.calendarPath: The server-relative path of the calendar where the event was created.
No binary data output is produced by this operation.
Dependencies
- Requires connection credentials to a CalDAV server, including a base URL and authentication (e.g., username/password or token).
- The base URL must include the protocol (
http://orhttps://) and point to the CalDAV server endpoint. - The node uses HTTP methods like PUT to interact with the CalDAV server.
- Proper permissions on the CalDAV server are required to create events in the specified calendar.
Troubleshooting
- Invalid Base URL: If the base URL in credentials is missing or does not start with
http://orhttps://, the node will throw an error. Ensure the URL includes the protocol and is correct. - Absolute URLs in Path Fields: Paths such as calendar paths must be server-relative (start with
/). Absolute URLs are rejected to prevent malformed requests. - Connection Errors:
ENOTFOUND: Hostname not found; verify the server address.ECONNREFUSED: Connection refused; check if the server is reachable and the port is open.ETIMEDOUT: Connection timed out; network issues or slow server response.
- HTTP Errors: Non-2xx responses indicate failure. The node reports the HTTP status code and message to help diagnose issues like permission denied or resource not found.
- Malformed iCalendar Data: Ensure the event data string is valid iCalendar format; otherwise, the server may reject the event.
Links and References
- CalDAV Protocol Specification (RFC 4791)
- iCalendar Format Specification (RFC 5545)
- n8n Expressions Documentation (for dynamic property values)