Actions15
Overview
This node connects to the Tripletex API v2 and allows users to manage orders within their Tripletex account. Specifically, the "Get" operation for the "Order" resource retrieves detailed information about a single order by its unique ID.
Common scenarios where this node is beneficial include:
- Fetching order details for review or processing in an automated workflow.
- Integrating order data into other systems such as CRMs, ERPs, or reporting tools.
- Automating follow-up actions based on order status or contents.
For example, a user can input an Order ID to retrieve all associated data like order date, delivery date, customer info, order lines, and currency, enabling seamless integration of order data into downstream processes.
Properties
| Name | Meaning |
|---|---|
| Order ID | The unique identifier of the order to retrieve. This property is required for the "Get" operation on the "Order" resource. |
Output
The output JSON contains the full order object as returned by the Tripletex API. This includes fields such as:
orderDate: The date when the order was placed.deliveryDate: Expected delivery date.customer: Object containing customer details including their ID.orderLines: Array of line items in the order, each with product ID, description, quantity, and unit price.currency: Currency code used for the order.
No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Tripletex API.
- The node uses the Tripletex API base URL, which switches between production and test environments based on credential configuration.
- HTTP requests are made with standard JSON content-type headers and Basic Authentication using a session token generated from the API key.
Troubleshooting
- Validation errors: If required parameters like "Order ID" are missing or empty, the node will throw validation errors before making the API call.
- Authentication failures: Errors related to invalid or expired API credentials may occur if the API key is incorrect or revoked.
- Not found errors: If the specified Order ID does not exist, the API will return an error indicating the order was not found.
- Network issues: Connectivity problems or incorrect environment settings can cause request failures.
To resolve these:
- Ensure the "Order ID" is correctly provided and valid.
- Verify that the API key credential is properly configured and active.
- Confirm network connectivity and correct environment selection (test vs production).
Links and References
- Tripletex API Documentation (official API docs)
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)