Actions2
- Address Book Actions
- Contact Actions
Overview
The CardDAV Node integrates with a CardDAV server to manage address books and contacts. Specifically, the "Get Contact" operation retrieves detailed information about a single contact from a specified address book on the CardDAV server. This node is useful in scenarios where you need to synchronize or access contact details stored remotely, such as importing contacts into a CRM, verifying contact information, or automating contact-related workflows.
Practical examples include:
- Fetching a contact's details by their unique ID to update records in another system.
- Retrieving contact information for sending personalized emails or notifications.
- Integrating with external address books to keep local databases up-to-date.
Properties
| Name | Meaning |
|---|---|
| Select Address Book or Set URL Name or ID | The address book from which to retrieve the contact. You can select an existing address book from a list or specify one dynamically using an expression (by URL or ID). This identifies the source address book on the CardDAV server. |
| File Name | The unique identifier (ID) of the contact to retrieve within the selected address book. This is required to fetch the specific contact's data. |
Output
The node outputs JSON data representing the retrieved contact's details. The structure typically includes all standard vCard fields available for that contact, such as name, email, phone numbers, addresses, and other contact metadata as provided by the CardDAV server.
If the node supports binary data output (not explicitly shown here), it would likely represent the raw vCard file or related attachments associated with the contact.
Dependencies
- Requires connection to a CardDAV server.
- Needs appropriate API credentials or authentication tokens configured in n8n to access the CardDAV server securely.
- The node depends on internal methods and actions defined in its bundled code to interact with the CardDAV protocol.
Troubleshooting
Common Issues:
- Incorrect or missing address book selection may cause the node to fail to find the contact.
- Providing an invalid or non-existent contact ID will result in no data or an error.
- Authentication failures due to incorrect or expired credentials.
- Network connectivity issues with the CardDAV server.
Error Messages:
- Errors indicating "unknown resource" suggest misconfiguration of the resource parameter.
- Authentication errors require checking the API key or token validity.
- If the node throws errors about missing parameters, ensure both the address book and contact ID are correctly set.