CardDAV icon

CardDAV

Interact with CardDAV servers for address book operations
Join our community

Actions5

Overview

This node integrates with CardDAV servers to manage address book contacts. Specifically, the Update Contact operation allows users to update an existing contact in a specified address book by providing updated contact data in vCard format.

Common scenarios for this node include synchronizing contact information from external systems, automating updates to user address books, or maintaining centralized contact lists programmatically.

For example, you might use this node to update a contact's phone number or email address stored on a CardDAV server whenever changes occur in your CRM system.

Properties

Name Meaning
Address Book Path The server-relative path to the address book containing the contact. Must start with "/". Spaces and special characters are automatically URL-encoded. Example: /addressbooks/user/contacts/
Contact ID Unique identifier of the contact to update. This corresponds to the contact's filename without extension. Example: contact-123
Contact Data (vCard) The updated contact information in vCard (.vcf) format. This string should contain the full vCard content representing the contact's details.

Output

The node outputs a JSON object with the following fields:

  • success (boolean): Indicates whether the update operation was successful (HTTP status code 2xx).
  • statusCode (number): The HTTP status code returned by the CardDAV server.
  • contactId (string): The identifier of the contact that was updated.
  • addressBookPath (string): The path of the address book where the contact resides.

No binary data is output by this operation.

Example output JSON:

{
  "success": true,
  "statusCode": 204,
  "contactId": "contact-123",
  "addressBookPath": "/addressbooks/user/contacts/"
}

Dependencies

  • Requires connection to a CardDAV server with valid credentials including a base URL starting with http:// or https://.
  • The node expects an API key or authentication token configured in the credentials to authorize requests.
  • The CardDAV server must support HTTP PUT requests to update vCard files at the specified paths.

Troubleshooting

  • Invalid Base URL in credentials: Ensure the base URL includes the protocol (http:// or https://) and points to the correct CardDAV server endpoint.
  • Absolute URLs not allowed in path fields: The Address Book Path must be a server-relative path starting with /. Do not provide full URLs here.
  • Host not found / Connection refused / Timeout errors: Verify network connectivity to the CardDAV server and that the server hostname and port are correct and accessible.
  • HTTP errors (non-2xx status codes): Check that the contact ID exists and that the provided vCard data is valid. Also verify permissions on the CardDAV server for updating contacts.
  • If the node throws errors related to URL encoding, ensure that the path and contact ID do not contain invalid characters; spaces and special characters will be auto-encoded but malformed input can cause issues.

Links and References

Discussion