Actions5
- Calendar Actions
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 workflows.
- Automating event processing based on calendar data.
- Filtering and retrieving events for reporting or notification purposes.
For example, you can use this node to fetch all upcoming events from your work calendar or retrieve events occurring on a particular day to trigger reminders.
Properties
| Name | Meaning |
|---|---|
| Calendar Name or ID | Select a calendar from the list or specify its ID/path manually. Represents the calendar to query. |
| Time Range | Choose the time range for event retrieval: "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) to retrieve events for that day. |
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 representing the event details.
statusCode: The HTTP status code returned by the CalDAV server for the request.
No binary data output is produced by this operation.
Dependencies
- Requires connection to a CalDAV server with valid credentials including a base URL.
- The base URL must include the protocol (
http://orhttps://) and be correctly configured in the credentials. - The node uses XML-based CalDAV requests (
PROPFIND,REPORT) to interact with the server. - n8n environment must have network access to the CalDAV server.
Troubleshooting
- Invalid Base URL: If the base URL in credentials is missing protocol or malformed, the node throws an error. Ensure the URL starts with
http://orhttps://. - Connection Errors: Errors like host not found, connection refused, or timeout indicate network or server accessibility issues. Verify server hostname, port, and network connectivity.
- Absolute URLs in Paths: Paths provided to the node must be server-relative (start with
/). Absolute URLs are rejected to prevent misconfiguration. - HTTP Errors: The node surfaces HTTP status codes and messages from the CalDAV server. Common errors include 404 (not found), 401 (unauthorized), or 403 (forbidden). Check credentials and permissions.
- Malformed XML Responses: If the server returns unexpected XML, event parsing may fail. Confirm server compatibility with CalDAV standards.