Actions28
Overview
This node integrates with the Dolibarr API to create an external user associated with a specific contact. It is useful in scenarios where you manage contacts in Dolibarr and want to programmatically create user accounts linked to those contacts, for example, to grant them access to a portal or system managed by Dolibarr.
Practical examples include:
- Automatically creating login credentials for new customers or partners stored as contacts.
- Synchronizing user accounts in Dolibarr with another system's user management.
- Bulk creation of external users based on existing contact records.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact in Dolibarr for which the external user will be created. Must be a positive integer. |
| Login | The username/login string for the new external user account. |
| Password | The password for the new external user account. This field is treated securely (password type). |
Output
The node outputs the full HTTP response from the Dolibarr API when creating the external user. The main output is a JSON object containing details about the newly created user or any error information returned by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an active Dolibarr API credential configured in n8n, including the base URL and an API authentication token.
- The node sends requests to the Dolibarr REST API endpoint
/contacts/{contactID}/createUser. - The API expects JSON content with
loginandpasswordfields in the request body.
Troubleshooting
Common issues:
- Invalid or missing Contact ID: Ensure the Contact ID exists in Dolibarr and is correctly provided.
- Authentication errors: Verify that the API credentials are valid and have sufficient permissions.
- Password policy violations: The Dolibarr API may enforce password complexity rules; ensure the password meets these requirements.
- Network or connectivity problems: Confirm that the Dolibarr instance is reachable from the n8n environment.
Error messages:
- HTTP 404 Not Found: Usually means the specified contact does not exist.
- HTTP 401 Unauthorized or 403 Forbidden: Indicates invalid or insufficient API credentials.
- Validation errors in response body: Check the login and password values for compliance with Dolibarr's requirements.
Resolving these typically involves verifying input parameters, checking API credentials, and reviewing Dolibarr server logs if accessible.
Links and References
- Dolibarr API Documentation – Official documentation for Dolibarr REST API endpoints.
- Dolibarr User Management – Information about users and permissions in Dolibarr.