CalDAV icon

CalDAV

CalDAV Node

Actions4

Overview

This node integrates with CalDAV-compatible calendar services to fetch calendar data. Specifically, the "Fetch" operation under the "Calendar" resource retrieves information about a specified calendar by its name. This is useful for workflows that need to access calendar details such as metadata or configuration before performing further actions like event management or synchronization.

Practical examples include:

  • Retrieving calendar details to display in a dashboard.
  • Validating the existence of a calendar before creating events.
  • Synchronizing calendar metadata with other systems.

Properties

Name Meaning
Calendar Name The exact name of the calendar to fetch. This identifies which calendar's data will be retrieved.

Output

The node outputs JSON data representing the fetched calendar's details. This typically includes metadata such as the calendar's unique identifier, display name, description, and possibly other attributes defined by the CalDAV service.

If the node supports binary data output (not evident from the provided code), it would represent attachments or calendar files, but this is not indicated here.

Dependencies

  • Requires an API key credential for authenticating with the CalDAV service.
  • The node depends on the CalDAV protocol and compatible calendar servers.
  • No additional environment variables are explicitly required based on the source code.

Troubleshooting

  • Common issues:

    • Incorrect or misspelled calendar name leading to no results or errors.
    • Authentication failures due to invalid or missing API credentials.
    • Network connectivity problems preventing access to the CalDAV server.
  • Error messages:

    • Errors indicating "calendar not found" suggest verifying the calendar name input.
    • Authentication errors require checking the configured API key or token.
    • Timeout or connection errors imply network or server availability issues.

Resolving these usually involves confirming the calendar name, ensuring valid credentials, and verifying network access.

Links and References

Discussion