Actions28
Overview
This node interacts with the Dolibarr API to retrieve contact information based on an email address. Specifically, the "Get By Mail" operation under the "Contact" resource fetches details of a contact by their email. This is useful in scenarios where you need to look up contact data dynamically during workflow execution, such as verifying user identity, enriching customer records, or automating communication processes.
Practical examples include:
- Automatically fetching contact details when a new email arrives.
- Enriching CRM records with additional contact info from Dolibarr.
- Validating if an email belongs to an existing contact before proceeding with further automation steps.
Properties
| Name | Meaning |
|---|---|
| The email address of the contact to retrieve. Must be a valid email string (e.g., name@email.com). | |
| Include Count | Boolean flag indicating whether to return the number of elements linked to this contact. Options: true or false. |
| Include Roles | Boolean flag indicating whether to include the roles associated with the contact. Options: true or false. |
Output
The node outputs JSON data representing the contact retrieved by the specified email. The structure typically includes all standard contact fields available in Dolibarr, such as name, email, phone numbers, and potentially linked entities depending on the flags set.
- If Include Count is enabled, the output will also contain a count of how many elements the contact is linked to.
- If Include Roles is enabled, the output will include role information related to the contact.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to a Dolibarr instance via its REST API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL of the Dolibarr API must be correctly set in the credentials.
Troubleshooting
Common Issues:
- Invalid or missing email input will cause the request to fail or return no results.
- Incorrect API credentials or base URL will result in authentication errors or connection failures.
- If the contact does not exist, the node may return an empty response or a 404 error.
Error Messages:
- Authentication errors indicate invalid or expired API keys; verify and update credentials.
- 404 Not Found errors suggest the email does not correspond to any contact; confirm the email value.
- Network or timeout errors require checking connectivity to the Dolibarr server.