Actions28
Overview
This node integrates with the Dolibarr API to manage contract lines, specifically allowing users to delete a line from a contract. It is useful in scenarios where contracts are managed programmatically and individual lines within those contracts need to be removed without deleting the entire contract.
For example, if a user wants to remove an obsolete or incorrect item line from a contract stored in Dolibarr, this node can perform that deletion by specifying the contract and line identifiers.
Properties
| Name | Meaning |
|---|---|
| Contract ID | The unique numeric identifier of the contract from which a line will be deleted. Must be a positive integer. |
| Line ID | The unique numeric identifier of the specific line within the contract to delete. Must be a positive integer. |
Output
The node outputs the full HTTP response from the Dolibarr API after attempting to delete the specified contract line. The json output field contains the API's response data, which typically confirms whether the deletion was successful or provides error details if it failed.
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 to authorize requests.
- The base URL of the Dolibarr API must be set in the node credentials.
Troubleshooting
Common Issues:
- Invalid or missing Contract ID or Line ID parameters will cause the request to fail.
- Network connectivity issues or incorrect API base URL configuration can prevent communication with Dolibarr.
- Insufficient permissions for the API key may result in authorization errors when attempting to delete lines.
Error Messages:
- 404 Not Found: The specified contract or line does not exist. Verify the IDs are correct.
- 401 Unauthorized: Authentication failed. Check the API credentials.
- 400 Bad Request: The input parameters might be invalid or malformed. Ensure Contract ID and Line ID are positive integers.
Resolving these usually involves verifying input values, checking API credentials, and ensuring the Dolibarr instance is accessible.
Links and References
- Dolibarr API Documentation (general reference for API endpoints)
- n8n Documentation (for configuring credentials and using HTTP-based nodes)