Actions15
Overview
This node interacts with calendar data via the CalDAV protocol. Specifically, the "Get" operation under the "Calendar" resource retrieves calendar information from a specified calendar URL path. This is useful for workflows that need to fetch calendar details or events from a CalDAV-compatible calendar server.
Practical examples include:
- Synchronizing calendar events into another system.
- Fetching calendar metadata for display or processing.
- Integrating calendar data into automated scheduling workflows.
Properties
| Name | Meaning |
|---|---|
| Calendar URL | The URL path of the calendar collection to access. Example: /calendars/user@example.com/personal/ |
Output
The node outputs JSON data representing the calendar information retrieved from the specified calendar URL. The exact structure depends on the CalDAV server response but typically includes calendar properties and event details.
If the node supports binary data output (not evident from the provided code), it would represent calendar files or attachments; however, this is not confirmed here.
Dependencies
- Requires access to a CalDAV-compatible calendar server.
- Needs an API authentication token or credentials configured in n8n to authenticate requests to the CalDAV server.
- The node relies on internal modules (
descriptionsandoperations) to define its behavior and execute operations.
Troubleshooting
- Invalid Calendar URL: If the calendar URL is incorrect or inaccessible, the node may fail to retrieve data. Verify the URL path and ensure the calendar exists.
- Authentication Errors: Missing or invalid credentials will cause authorization failures. Ensure proper API keys or tokens are configured.
- Network Issues: Connectivity problems to the CalDAV server can cause timeouts or errors.
- Unsupported Server Responses: If the CalDAV server returns unexpected data formats, the node might not parse the response correctly.