Actions28
Overview
This node integrates with the Dolibarr API to manage contracts. Specifically, the "Delete" operation under the "Contracts" resource allows users to delete a contract by its unique identifier. This is useful in scenarios where contracts are no longer valid or need to be removed from the system to maintain data accuracy.
Practical examples include:
- Automatically deleting expired contracts as part of a cleanup workflow.
- Removing contracts that were created in error.
- Integrating contract deletion into broader business process automations.
Properties
| Name | Meaning |
|---|---|
| Contract ID | The unique numeric identifier of the contract to delete. Must be an integer greater than 0. |
Output
The node outputs the full HTTP response from the Dolibarr API after attempting to delete the specified contract. The output is available in the json field and typically contains information about the success or failure of the deletion request.
If the API supports it, the node may also return binary data, but based on the provided code and operation, the primary output is JSON indicating the result of the delete action.
Dependencies
- Requires an active connection to a Dolibarr instance via its REST API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The base URL for the Dolibarr API must be set in the credentials configuration.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Contract ID will likely result in an error or no action.
- Network connectivity problems or incorrect API base URL can cause request failures.
- Insufficient permissions or invalid API credentials will prevent successful deletion.
Error messages:
- Errors related to HTTP status codes (e.g., 404 Not Found) indicate the contract does not exist.
- Authentication errors (e.g., 401 Unauthorized) suggest issues with the API key or token.
Resolutions:
- Verify the Contract ID exists in Dolibarr before attempting deletion.
- Check and update API credentials and ensure they have sufficient permissions.
- Confirm the API base URL is correct and accessible from the n8n environment.