Actions28
Overview
This node interacts with the Dolibarr API to unactivate a specific line within a contract. It is useful in scenarios where you need to mark a contract line as no longer active from a certain start date, optionally adding a comment explaining the reason for unactivation.
Practical examples include:
- Temporarily suspending a service line on a contract without deleting it.
- Marking a contract line as inactive due to changes in client requirements or contract terms.
- Automating contract lifecycle management by programmatically controlling line activation status.
Properties
| Name | Meaning |
|---|---|
| Contract ID | The unique identifier of the contract containing the line to be unactivated. |
| Line ID | The unique identifier of the specific line within the contract to unactivate. |
| Start Date | The date and time from which the line should be considered unactivated (required). |
| Comment | An optional text comment providing additional context or explanation for the action. |
Output
The node outputs JSON data representing the response from the Dolibarr API after attempting to unactivate the specified contract line. This typically includes confirmation of the operation's success or details about any errors encountered.
No binary data output is involved.
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 will cause the API call to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Providing a Start Date in an incorrect format may lead to request rejection.
- Network connectivity problems can prevent communication with the Dolibarr API.
Error messages and resolutions:
- 401 Unauthorized: Check that the API key or token is correctly configured and has sufficient permissions.
- 404 Not Found: Verify that the Contract ID and Line ID exist and are correct.
- 400 Bad Request: Ensure the Start Date is provided and formatted properly; also check for required fields.
- 500 Internal Server Error: May indicate server-side issues; retry later or contact Dolibarr support.
Links and References
- Dolibarr API Documentation
- n8n Documentation on HTTP Request Node (for understanding API calls)