CalDAV icon

CalDAV

Interact with CalDAV servers for calendar operations

Overview

This node integrates with CalDAV servers to perform calendar-related operations. Specifically, the Get Events operation retrieves events from a specified calendar within a given time range. It supports fetching all events, events within a date range, or events on a specific date.

Common scenarios include:

  • Synchronizing calendar events from a CalDAV server into other systems.
  • Automating workflows based on upcoming calendar events.
  • Extracting event data for reporting or notifications.

For example, you can use this node to fetch all events from your work calendar for the next week and send reminders via email or chat.

Properties

Name Meaning
Calendar Name or ID Select a calendar from the list or specify its ID/path. This identifies which calendar to query.
Time Range Choose the time range of events to retrieve: "All Events", "Date Range", or "Specific Date".
Start Date (Shown if "Date Range" selected) The start date/time (ISO format) for filtering events.
End Date (Shown if "Date Range" selected) The end date/time (ISO format) for filtering events.
Date (Shown if "Specific Date" selected) The specific date (ISO format) for which to retrieve events.

Output

The node outputs JSON data containing:

  • events: An array of event objects, each including:

    • href: The resource path of the event.
    • etag: The entity tag for versioning.
    • calendarData: The raw iCalendar data string for the event.
  • statusCode: The HTTP status code returned by the CalDAV server.

This output allows downstream nodes to parse event details or handle them as needed.

Dependencies

  • Requires connection credentials to a CalDAV server, including a base URL with protocol (http:// or https://).
  • The node uses XML-based CalDAV REPORT requests to query events.
  • No additional external services are required beyond the CalDAV server.
  • Proper authentication credentials must be configured in n8n for the CalDAV server.

Troubleshooting

  • Invalid Base URL: If the base URL in credentials is missing protocol or malformed, the node will throw an error. Ensure it starts with http:// or https://.
  • Connection Errors: Errors like host not found, connection refused, or timeout indicate network or server issues. Verify server accessibility and credentials.
  • Absolute URLs in Paths: Paths must be server-relative starting with /. Absolute URLs in path parameters cause errors.
  • HTTP Errors: The node surfaces HTTP status codes and messages from the CalDAV server. Common issues include authorization failures or invalid requests.
  • Empty Event Results: If no events are returned, verify the calendar path and time range filters.

Links and References

Discussion