Actions28
Overview
This node updates an existing Contact in Dolibarr, a popular open-source ERP and CRM system. It allows users to modify various contact details such as name, email, phone numbers, address, job position, and custom extra fields. This operation is useful when you need to keep your contact information up-to-date automatically, for example syncing contacts from another system or updating details after receiving new information.
Practical examples:
- Automatically update a contact’s phone number and email after a customer submits a form.
- Change the assigned third-party company or job position of a contact based on changes in your CRM.
- Add or modify custom attributes (extra fields) for contacts to store additional business-specific data.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique numeric identifier of the contact to update (required). |
| Last Name | Contact's last name or label. |
| First Name | Contact's first name. |
| Third-Party Name or ID | The associated third-party company, selectable by list, URL, or direct ID. |
| Civility Name or ID | Contact's civility (e.g., Mr, Mrs), selectable from a list or by ID. |
| Job Position | Contact's job title or position. |
| Contact's email address. | |
| Address | Contact's street address. |
| Zip Code | Contact's postal code. |
| City | Contact's city or town. |
| Country Name or ID | Contact's country, selectable from a list or by ID. |
| State/Province Name or ID | Contact's state or province, selectable from a list or by ID. |
| Business Phone Number | Contact's professional phone number. |
| Mobile Phone Number | Contact's mobile phone number. |
| Personal Phone Number | Contact's personal phone number. |
| Fax Phone Number | Contact's fax number. |
| Private | Boolean flag indicating if the contact is private (true/false). |
| Date Of Birth | Contact's birth date. |
| Birthday Alert | Boolean flag to enable birthday alert for the contact (true/false). |
| Extra Fields | Custom attribute fields allowing multiple key-value pairs to be updated. |
| Fields | Other contract fields (advanced usage, not detailed here). |
Output
The node outputs the full HTTP response from the Dolibarr API after attempting to update the contact. The main output is JSON containing the updated contact data or error information if the update failed.
If the update is successful, the JSON typically includes the updated contact properties reflecting the changes made.
No binary data output is involved in this operation.
Dependencies
- Requires an active Dolibarr API connection with proper authentication credentials (API key or token).
- The base URL of the Dolibarr instance must be configured in the credentials.
- The node uses Dolibarr REST API endpoints to perform the update (
PUT /contacts/{contactID}).
Troubleshooting
- Invalid Contact ID: If the provided Contact ID does not exist, the API will return a 404 error. Verify the Contact ID before running the node.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key/token is correctly set in the credentials.
- Validation Errors: Providing invalid values for fields (e.g., malformed email, invalid URLs for third-party) may cause the API to reject the request. Double-check input formats.
- Missing Required Fields: Contact ID is mandatory; omitting it will prevent the update.
- Extra Fields Loading: If extra fields do not load properly, check that the Dolibarr user has permissions to access extrafields and that the API endpoint is reachable.