Actions28
Overview
This node integrates with the Dolibarr API to retrieve detailed information about a specific contact. It is designed to fetch data for a single contact by its unique identifier, optionally including additional metadata such as the count of linked elements and the roles associated with the contact.
Common scenarios where this node is beneficial include:
- Fetching contact details for customer management or CRM workflows.
- Retrieving contact roles and usage counts to understand relationships and dependencies within Dolibarr.
- Automating updates or synchronization of contact data between Dolibarr and other systems.
Practical example:
- A workflow that triggers when a new order is created, fetching the contact details of the customer placing the order to personalize communications or update external databases.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique numeric identifier of the contact to retrieve. Must be an integer greater than 0. |
| Include Count | Boolean flag indicating whether to return the number of elements where the contact is linked. |
| Include Roles | Boolean flag indicating whether to include the roles associated with the contact in the output. |
Output
The node outputs JSON data representing the contact's details as returned by the Dolibarr API. This includes standard contact fields such as name, address, email, phone numbers, and potentially extended information depending on the flags set:
- If Include Count is true, the output will contain a field indicating how many elements reference this contact.
- If Include Roles is true, the output will include the roles assigned to the contact.
No binary data output is produced by this node.
Dependencies
- Requires access to a Dolibarr instance with API enabled.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL of the Dolibarr API must be provided in the credential configuration.
Troubleshooting
Error: Contact not found (404)
Occurs if the specified Contact ID does not exist. Verify the Contact ID is correct and exists in Dolibarr.Authentication errors (401/403)
Ensure the API credentials are valid and have sufficient permissions to access contact data.Network or connection issues
Confirm that the Dolibarr API endpoint is reachable from the n8n environment and that no firewall or proxy blocks the request.Invalid input errors
Make sure the Contact ID is a positive integer and required properties are set.