CalDAV icon

CalDAV

Interact with CalDAV servers for calendar operations
Join our community

Actions5

Overview

This node enables interaction with CalDAV servers to manage calendar data. Specifically, the Get Calendars operation retrieves a list of calendars available under a specified calendar home set path on the CalDAV server.

Typical use cases include:

  • Synchronizing calendars from a CalDAV server into n8n workflows.
  • Listing all user calendars for selection or further processing.
  • Integrating calendar data from self-hosted or third-party CalDAV services into automation pipelines.

For example, you can use this node to fetch all calendars from your CalDAV server and then trigger workflows based on events in those calendars.

Properties

Name Meaning
Calendar Home Set Path to the calendar home set on the CalDAV server. Must start with "/". Spaces and special characters are automatically encoded. Default is /calendars/user/.

Output

The output JSON contains:

  • calendars: An array of calendar objects, each with:

    • href: The decoded URL path of the calendar.
    • displayName: The display name of the calendar (if available).
    • description: The calendar description (if available).

  • statusCode: The HTTP status code returned by the CalDAV server for the PROPFIND request.

Example output structure:

{
  "calendars": [
    {
      "href": "/calendars/user/calendar1/",
      "displayName": "Work",
      "description": "Work related events"
    },
    {
      "href": "/calendars/user/calendar2/",
      "displayName": "Personal",
      "description": "Personal appointments"
    }
  ],
  "statusCode": 207
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential configured with the CalDAV server base URL.
  • The base URL must include the protocol (http:// or https://) and be correctly set in the credentials.
  • The node uses HTTP methods like PROPFIND to communicate with the CalDAV server.
  • Proper authentication credentials for the CalDAV server are mandatory.

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 correct.
  • Absolute URLs in paths: Paths provided as input must be server-relative (start with /). Absolute URLs in path fields cause errors.
  • Connection errors:
    • ENOTFOUND: Hostname not found — check the server address.
    • ECONNREFUSED: Connection refused — server may be down or port blocked.
    • ETIMEDOUT: Connection timed out — network issues or slow server.
  • HTTP errors: The node surfaces HTTP status codes and messages from the CalDAV server. Common issues include authentication failures or permission errors.
  • To debug, verify credentials, server URL, and network connectivity.

Links and References

Discussion