Actions15
Overview
This node connects to the Tripletex API v2 and allows users to interact with various resources such as customers, products, orders, inventory, invoices, and webhooks. Specifically, for the Order resource with the Get All operation, it retrieves a list of orders from the Tripletex system.
This operation supports pagination, field selection, and sorting, making it useful for scenarios where you need to fetch multiple orders efficiently, such as syncing order data into another system, generating reports, or performing batch processing on orders.
Practical example:
A business using Tripletex for order management can use this node to pull all recent orders (e.g., starting from index 0, limiting to 100 results) sorted by order date descending, and then process them in n8n workflows for invoicing or shipment preparation.
Properties
| Name | Meaning |
|---|---|
| From | Starting index for pagination; defines the offset from which to start fetching orders. |
| Limit | Maximum number of orders to return in one request; controls page size. |
| Fields | Comma-separated list of specific fields to include in the response; filters returned data. |
| Sorting | Sorting criteria for the results; e.g., "name" for ascending or "-name" for descending. |
Output
The output is a JSON object containing the retrieved orders data as returned by the Tripletex API. The structure depends on the API response but typically includes an array of order objects with their details such as order date, delivery date, customer info, order lines, currency, etc.
No binary data is output by this operation.
Example snippet of output JSON might look like:
{
"orders": [
{
"id": 123,
"orderDate": "2024-01-01T12:00:00Z",
"deliveryDate": "2024-01-05T12:00:00Z",
"customer": { "id": 456, "name": "Customer A" },
"orderLines": [
{
"productId": 789,
"description": "Product description",
"quantity": 2,
"unitPrice": 100
}
],
"currency": "NOK"
}
// more orders...
]
}
Dependencies
- Requires an API key credential for authenticating with the Tripletex API.
- The node uses the Tripletex API base URL, which switches between test and production environments based on the credential configuration.
- No additional external dependencies are required beyond the HTTP request helper provided by n8n.
Troubleshooting
- Validation errors: If required parameters are missing (not applicable specifically for Get All, but relevant for create/update operations), the node will throw validation errors listing missing fields.
- Authentication errors: If the API key or session token is invalid or expired, requests will fail with authentication errors. Ensure the API credentials are correctly configured and valid.
- Pagination issues: Setting
FromorLimitincorrectly may result in empty responses or incomplete data. Adjust these values according to the total number of orders expected. - Sorting/Fields syntax: Incorrect formatting in the
SortingorFieldsproperties may cause API errors or unexpected results. Use proper comma-separated lists and prefix with-for descending sort.
Links and References
- Tripletex API Documentation (official API docs for detailed endpoint info)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests work in n8n)
- Tripletex Official Website