Actions15
Overview
The node integrates with the Tripletex API v2 to manage orders. Specifically, the Update Order operation allows users to modify existing order records by specifying the order ID and new details such as order date, delivery date, customer, order lines, and currency.
This node is beneficial in scenarios where order information needs to be corrected or updated after creation, for example:
- Changing the expected delivery date due to supply chain delays.
- Updating quantities or prices of products in an order.
- Correcting the customer associated with an order.
Practical example: A business receives a customer request to change the delivery date and add more items to an existing order. Using this node’s update operation, the workflow can programmatically apply these changes in Tripletex without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Order ID | The unique identifier of the order to update (required). |
| Order Date | The date when the order was placed (required). |
| Delivery Date | The expected delivery date for the order (optional). |
| Customer ID | The identifier of the customer placing the order (required). |
| Order Lines | Collection of line items in the order. Each line includes: - Product ID (required) - Description (optional) - Quantity ordered (required) - Unit price per item (required) |
| Currency | The currency code for the order amounts, e.g., "NOK" (default is "NOK"). |
Output
The node outputs JSON data representing the response from the Tripletex API after updating the order. This typically includes the updated order details as confirmed by the API.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Tripletex API.
- The node uses the Tripletex environment setting to determine whether to connect to the test or production API endpoint.
- Network access to
https://api.tripletex.no(production) orhttps://api-test.tripletex.tech(test) is required.
Troubleshooting
- Validation errors: If required fields like Order ID, Order Date, or Customer ID are missing, the node will throw validation errors such as "Order date is required" or "Customer ID is required". Ensure all mandatory properties are set.
- Authentication failures: Errors related to invalid or missing API credentials may occur. Verify that the API key credential is correctly configured and has necessary permissions.
- API errors: The Tripletex API might return errors if the order ID does not exist or if the payload contains invalid data. Check the error message returned in the node output for details.
- Network issues: Connectivity problems to the Tripletex API endpoints can cause timeouts or failures. Confirm network access and proxy settings if applicable.
Links and References
- Tripletex API Documentation (official API docs)
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)