Actions15
Overview
This node connects to the Tripletex API v2 and allows you to manage orders within the Tripletex system. Specifically, the "Get" operation for the "Order" resource retrieves detailed information about a single order by its ID.
Common scenarios where this node is beneficial include:
- Fetching order details to display or process in workflows.
- Integrating order data from Tripletex into other systems or reports.
- Automating order status checks or validations.
For example, you can use this node to get an order's full details by providing its Order ID, then use that data downstream in your workflow for invoicing or shipping processes.
Properties
| Name | Meaning |
|---|---|
| Order ID | The unique identifier of the order to retrieve. This is required to specify which order to fetch. |
Output
The output of the node is a JSON object representing the order data returned by the Tripletex API. It includes all available fields for the order identified by the provided Order ID, such as order date, delivery date, customer info, order lines, currency, and other order-specific details.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Tripletex API.
- The node uses the Tripletex API base URL, which switches between a test environment and production based on the configured credential environment.
- No additional external dependencies are needed beyond HTTP access to the Tripletex API.
Troubleshooting
- Validation errors: If the Order ID is missing or empty, the node will throw a validation error indicating that the Order ID is required.
- Authentication errors: Ensure the API key credential is correctly configured and has permissions to access order data.
- Network or API errors: Check network connectivity and Tripletex API status if requests fail.
- Unsupported operations: Using an unsupported operation or resource combination will result in an error.
Links and References
- Tripletex API Documentation (official API docs for more details on order endpoints)
- n8n documentation on creating custom nodes