Actions28
Overview
This node interacts with the Dolibarr API to manage contacts and their categories. Specifically, the "Delete Categories" operation under the "Contact" resource allows users to remove a category association from a specified contact. This is useful in scenarios where you want to update or clean up contact categorizations, for example, removing outdated or incorrect category tags from a contact record.
Practical examples:
- Removing a "VIP" category from a customer who no longer qualifies.
- Cleaning up categories after a contact's status changes.
- Automating category management as part of a larger workflow that updates contact information.
Properties
Name | Meaning |
---|---|
Contact ID | The unique identifier (number) of the contact from which the category will be deleted. |
Category ID | The unique identifier (number) of the category to delete from the specified contact. |
Output
The node outputs the full HTTP response from the Dolibarr API after attempting to delete the category from the contact. The output is available in the json
field and typically contains confirmation of the deletion or an error message if the operation failed.
No binary data output is involved in 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 set correctly in the node credentials.
Troubleshooting
Common issues:
- Invalid or missing Contact ID or Category ID will cause the API call to fail.
- Network connectivity problems or incorrect API base URL configuration can prevent successful communication.
- Insufficient permissions on the API key may result in authorization errors.
Error messages:
- HTTP 404 Not Found: The specified contact or category does not exist. Verify IDs.
- HTTP 401 Unauthorized: Authentication failed; check API credentials.
- HTTP 400 Bad Request: Likely due to invalid parameter values; ensure IDs are positive integers.
Resolving these usually involves verifying input parameters, checking API credentials, and ensuring the Dolibarr instance is accessible.