CalDAV icon

CalDAV

Interact with CalDAV servers for calendar operations

Actions5

Overview

This node integrates with CalDAV servers to manage calendar data, specifically allowing users to create, update, retrieve, and delete calendar events. The "Create Event" operation enables adding new events to a specified calendar by uploading event details formatted in the iCalendar (.ics) standard.

Common scenarios for this node include:

  • Automating event creation in corporate or personal calendars hosted on CalDAV-compatible servers.
  • Syncing events from other systems into a centralized calendar.
  • Programmatically managing calendar schedules without manual entry.

For example, you can use this node to automatically add meeting invites generated from form submissions or CRM triggers directly into your CalDAV calendar.

Properties

Name Meaning
Calendar Name or ID Select the target calendar from a list or specify its server-relative path (e.g., /calendars/user/calendar/). This identifies where the event will be created.
Event ID A unique identifier string for the event, used as the filename (with .ics extension) on the server. Example: event-123.
Event Data (iCalendar) The full event details in iCalendar (.ics) format. This string contains all event information such as start/end times, summary, description, attendees, etc.

Output

The node outputs a JSON object containing:

  • success: Boolean indicating if the event creation was successful (HTTP status code 2xx).
  • statusCode: The HTTP response status code from the CalDAV server.
  • eventId: The event identifier used in the request.
  • calendarPath: The calendar path where the event was created.

No binary data output is produced by this operation.

Example output JSON:

{
  "success": true,
  "statusCode": 201,
  "eventId": "event-123",
  "calendarPath": "/calendars/user/calendar/"
}

Dependencies

  • Requires connection credentials to a CalDAV server, including a base URL and authentication token or API key.
  • The base URL must include the protocol (http:// or https://) and point to the CalDAV server endpoint.
  • The node uses HTTP methods like PUT to upload .ics files representing events.
  • Proper permissions on the CalDAV server are necessary 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:// or https://, the node will throw an error. Ensure the URL includes the protocol and is correctly formatted.
  • Absolute URLs in Paths: The calendar path and event paths must be server-relative (start with /). Absolute URLs are rejected to prevent malformed requests.
  • Connection Errors: Errors like host not found, connection refused, or timeout indicate network or server accessibility issues. Verify server address, port, and network connectivity.
  • HTTP Errors: Non-success HTTP status codes (non-2xx) may indicate permission issues, invalid event data, or server errors. Check the server logs and ensure the event data conforms to iCalendar standards.
  • Encoding Issues: The node encodes path components safely; however, malformed input strings might cause errors. Validate inputs before use.

Links and References

Discussion