Actions28
Overview
This node updates an existing Contact in Dolibarr via its API. It is useful when you want to modify details of a contact record, such as changing the name, email, address, phone numbers, or custom extra fields.
Common scenarios include:
- Synchronizing updated contact information from another system into Dolibarr.
- Correcting or enriching contact data stored in Dolibarr.
- Automating bulk updates of contacts based on external triggers or workflows.
For example, you could use this node to update a contact’s email and phone number after receiving new data from a CRM or form submission.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique numeric identifier of the contact to update. Must be a positive integer. |
| Values | A collection of fields to update on the contact. These include: |
| - Last Name | Contact's last name or label (string). |
| - First Name | Contact's first name (string). |
| - Third-Party Name or ID | Reference to the related third-party entity. Can be selected from a searchable list, specified by URL containing the third-party ID, or directly by ID. This links the contact to a company or organization. |
| - Civility Name or ID | Contact's civility (e.g., Mr, Mrs), selectable from a loaded list or specified by ID. |
| - Job Position | Contact's job title or position (string). |
| Contact's email address (string). | |
| - Address | Contact's street address (string). |
| - Zip Code | Postal code for the contact's address (string). |
| - City | City or town of the contact's address (string). |
| - Country Name or ID | Country of the contact, selectable from a loaded list or specified by ID. |
| - State/Province Name or ID | State or province of the contact, selectable from a loaded list or specified by ID. |
| - Business Phone Number | Contact's business phone number (string). |
| - Mobile Phone Number | Contact's mobile phone number (string). |
| - Personal Phone Number | Contact's personal phone number (string). |
| - Fax Phone Number | Contact's fax number (string). |
| - Private | Boolean flag indicating if the contact is private (true/false). |
| - Date Of Birth | Contact's date of birth (dateTime). |
| - Birthday Alert | Boolean flag to enable birthday alert for the contact (true/false). |
| Extra Fields | Multiple custom attributes can be set here. Each attribute consists of a field name (loaded dynamically) and a corresponding value (string). |
| Fields | Other contract-related fields (not detailed here, but available for assignment). |
Output
The node outputs the full JSON response returned by the Dolibarr API after updating the contact. This typically includes the updated contact object with all its properties reflecting the changes made.
If the API returns binary data (unlikely for this operation), it would represent associated files or attachments related to the contact, but this node primarily deals with JSON data.
Dependencies
- Requires an active connection to a Dolibarr instance with API access enabled.
- Needs an API authentication credential configured in n8n (an API key or token).
- The base URL of the Dolibarr API must be provided in the credentials.
- Uses Dolibarr API endpoints for contacts and related dictionaries (civilities, countries, states).
Troubleshooting
- Invalid Contact ID: If the Contact ID does not exist or is invalid, the API will likely return a 404 error. Verify the ID before running the node.
- Authentication Errors: Ensure the API credentials are correct and have sufficient permissions to update contacts.
- Validation Errors: Some fields require specific formats (e.g., email, URLs for third-party references). Invalid inputs may cause the API to reject the request.
- Missing Required Fields: Contact ID is mandatory; omitting it will prevent the update.
- API Rate Limits or Downtime: Network issues or API limits may cause failures; retry or check Dolibarr server status.
- Extra Fields Loading: If extra fields do not load properly, verify that the Dolibarr instance supports extrafields and the API user has access.
Links and References
This summary is based solely on static analysis of the provided source code and property definitions.