CardDAV icon

CardDAV

Interact with CardDAV servers for address book operations
Join our community

Actions5

Overview

This node interacts with CardDAV servers to manage address book data. Specifically, the Delete Contact operation removes a contact from a specified address book on a CardDAV server. This is useful in scenarios where you want to automate contact management, such as cleaning up outdated contacts or synchronizing contact lists by removing entries programmatically.

For example, you might use this node to delete a contact identified by its unique ID from a user's address book path on your CardDAV-compatible server.

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 The unique identifier of the contact to delete. Example: contact-123

Output

The node outputs a JSON object with the following fields:

  • success: A boolean indicating whether the deletion was successful (true if HTTP status code is 2xx).
  • statusCode: The HTTP status code returned by the CardDAV server for the delete request.
  • contactId: The ID of the contact that was requested to be deleted.
  • addressBookPath: The normalized path of the address book from which the contact was deleted.

No binary data output is produced by this operation.

Example output JSON:

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

Dependencies

  • Requires an API key credential configured with the CardDAV server base URL and authentication details.
  • The base URL must include the protocol (http:// or https://) and be valid.
  • The node uses HTTP DELETE requests to interact with the CardDAV server.

Troubleshooting

  • Invalid Base URL: If the base URL in credentials is missing or does not start with http:// or https://, the node will throw an error. Ensure the URL includes the protocol and is correctly formatted.
  • Absolute URLs in Paths: The address book path must be server-relative (start with /). Absolute URLs are not allowed and will cause errors.
  • Host Not Found: If the server hostname is incorrect or unreachable, expect a "Host not found" error. Verify the server address in credentials.
  • Connection Refused or Timed Out: Network issues or firewall restrictions may cause connection refused or timeout errors. Check network connectivity and server availability.
  • HTTP Errors: Non-success HTTP status codes will be reported in the output. For example, 404 means the contact or path was not found; 403 indicates permission issues.

Links and References

Discussion