CalDav Calendar

Work with CalDav/CardDav servers (Baikal, SabreDAV, etc)

Actions4

Overview

This node interacts with CalDav servers to manage calendar events. Specifically, the Update Event operation allows users to modify an existing event in a specified calendar by providing the calendar URL, the event's unique identifier, and the new event data.

Common scenarios include:

  • Updating meeting details such as time, location, or description on a shared calendar.
  • Modifying reminders or attendees for an event.
  • Synchronizing event changes from other systems into a CalDav calendar.

Practical example:

  • A user wants to update the title and start time of a calendar event after receiving updated information from a CRM system. They provide the calendar URL, event ID, and the updated event JSON data to this node, which then applies the changes on the CalDav server.

Properties

Name Meaning
Calendar URL URL of the calendar (DAV collection) where the event resides.
Event ID Unique identifier of the event to update within the specified calendar.
Event Data JSON object containing the updated event details to apply.

Output

The node outputs a JSON object representing the updated event as returned by the CalDav server. This typically includes all event properties after modification, confirming the successful update.

No binary data output is produced by this operation.

Dependencies

  • Requires connection credentials to a CalDav/CardDav server supporting basic authentication.
  • The node depends on an API key or authentication token configured in n8n credentials to access the CalDav server.
  • The calendar URL must point to a valid DAV collection on the server.
  • The node uses internal helper functions to communicate with the CalDav server via its API.

Troubleshooting

  • Common issues:

    • Invalid or expired credentials leading to authentication failures.
    • Incorrect calendar URL causing inability to locate the calendar.
    • Non-existent or incorrect event ID resulting in "event not found" errors.
    • Malformed JSON in the event data causing update failures.
  • Error messages and resolutions:

    • "No credentials found": Ensure that the required API authentication credential is properly set up in n8n.
    • "Event not found" or similar: Verify the event ID and calendar URL are correct and that the event exists.
    • JSON parsing errors: Validate the event data JSON structure before passing it to the node.
    • Network or permission errors: Confirm network connectivity and that the authenticated user has write permissions on the calendar.

Links and References

Discussion