Actions28
Overview
This node interacts with the Dolibarr API to retrieve detailed information about a specific contract by its ID. It is useful in scenarios where you need to fetch contract data for further processing, reporting, or integration with other systems. For example, you might use this node to get contract details before updating a CRM record or generating a contract summary document.
Properties
| Name | Meaning |
|---|---|
| Contract ID | The unique numeric identifier of the contract to retrieve. Must be an integer greater than or equal to 1. |
Output
The node outputs the full JSON response from the Dolibarr API containing the contract details. This typically includes all fields related to the contract such as contract terms, parties involved, dates, status, and any custom fields defined in Dolibarr.
If the API supports it, the output may also include metadata or HTTP response details because the request is configured to return the full response.
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 of the Dolibarr API must be set in the credentials configuration.
Troubleshooting
Common issues:
- Invalid or missing Contract ID will cause the API call to fail.
- Incorrect or expired API credentials will result in authentication errors.
- Network connectivity problems can prevent reaching the Dolibarr server.
- If the contract ID does not exist, the API may return a 404 error.
Error messages:
- Authentication errors usually indicate invalid API keys or tokens; verify and update credentials.
- 404 Not Found means the specified contract ID does not exist; check the ID value.
- Timeout or network errors suggest connectivity issues; ensure the Dolibarr server is reachable.
Links and References
- Dolibarr API Documentation (general reference for API endpoints and usage)