Actions28
Overview
This node integrates with the Dolibarr API to manage contacts within the Dolibarr system. Specifically, the "Delete Contact" operation allows users to remove a contact by specifying its unique Contact ID. This is useful in scenarios where outdated or incorrect contact information needs to be purged from the system to maintain data accuracy.
Practical examples include:
- Automatically deleting contacts that have unsubscribed or are no longer relevant.
- Cleaning up test or duplicate contacts during data synchronization workflows.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique numeric identifier of the contact to delete. Must be an integer greater than or equal to 1. |
Output
The node outputs the full HTTP response from the Dolibarr API after attempting to delete the specified contact. The output is available in the json field and typically contains status information about the deletion request.
If the deletion is successful, the response usually confirms the removal of the contact. If unsuccessful, error details will be included in the response.
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 or key configured in n8n credentials for Dolibarr.
- The base URL of the Dolibarr API must be set correctly in the credentials.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Contact ID will result in an error from the API.
- Network connectivity problems or incorrect API base URL configuration can cause request failures.
- Insufficient permissions associated with the API token may prevent deletion.
Error messages:
- 404 Not Found: The specified Contact ID does not exist. Verify the ID before retrying.
- 401 Unauthorized: Authentication failed. Check the API credentials and permissions.
- 400 Bad Request: The Contact ID parameter might be missing or invalid. Ensure it is a positive integer.
Resolving these errors typically involves verifying the Contact ID, checking API credentials, and ensuring network access to the Dolibarr server.