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 kept current, for example:
- Updating delivery dates due to shipping delays.
- Correcting or adding order line items after an order has been placed.
- Changing the customer associated with an order.
- Adjusting currency or pricing details on an existing order.
Practical example: An e-commerce platform uses this node to update orders when customers request changes or when logistics updates delivery schedules.
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 who placed the order (required). |
| Order Lines | A collection of order line items, each including: - Product ID (required) - Description (optional) - Quantity ordered (required) - Unit price per item (required) |
| Currency | The currency code for the order amounts, defaulting to "NOK" if not specified. |
Output
The node outputs a JSON object representing the updated order as returned by the Tripletex API. This typically includes all order details such as order ID, dates, customer info, order lines, currency, and any other metadata provided 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 connectivity to the Tripletex API endpoints is necessary.
Troubleshooting
- Validation errors: If required fields like Order ID, Order Date, or Customer ID are missing, the node will throw validation errors indicating which fields are required.
- Authentication failures: Ensure that the API key credential is correctly configured and valid.
- API errors: Errors from the Tripletex API (e.g., invalid order ID, permission issues) will be returned in the node's error output if "Continue On Fail" is enabled; otherwise, they will stop execution.
- Incorrect field formats: Dates should be provided in ISO 8601 format; incorrect formatting may cause API rejections.
Links and References
- Tripletex API Documentation (official API docs for reference)
- n8n documentation on creating custom nodes