Actions28
Overview
This node integrates with the Dolibarr API to retrieve detailed information about a specific contact by its ID. It is useful in scenarios where you need to fetch contact details from Dolibarr for further processing, reporting, or synchronization with other systems.
Practical examples include:
- Retrieving a contact's full profile before updating records in a CRM.
- Fetching contact roles and usage counts to analyze relationships and dependencies within Dolibarr.
- Using contact data to trigger workflows based on specific contact attributes.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to retrieve. Must be a positive integer (minimum 1). |
| Include Count | Whether to include the number of elements that reference this contact as a link. Options: true or false. |
| Include Roles | Whether to include the roles associated with the contact. Options: true or false. |
Output
The node outputs JSON data representing the contact retrieved from Dolibarr. This includes all standard contact fields plus optionally:
- A count of linked elements if "Include Count" is enabled.
- Roles associated with the contact if "Include Roles" is enabled.
The output structure corresponds directly to the Dolibarr API response for a single contact resource. No binary data output is produced by this operation.
Dependencies
- Requires an active connection to a Dolibarr instance via its REST API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL of the Dolibarr API must be set in the credentials configuration.
Troubleshooting
- Invalid Contact ID: If the provided Contact ID does not exist or is invalid, the API may return a 404 error. Verify the ID is correct and exists in Dolibarr.
- Authentication Errors: Missing or incorrect API credentials will cause authorization failures. Ensure the API key/token is valid and has sufficient permissions.
- Network Issues: Connectivity problems to the Dolibarr server will result in request timeouts or errors. Check network access and API endpoint availability.
- Unexpected Response Format: If Dolibarr API changes or returns unexpected data, the node might fail to parse the response correctly. Confirm API version compatibility.