Tripletex

Connect to Tripletex API v2
Join our community

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 is useful when you want to fetch multiple orders in bulk, for example:

  • To synchronize order data into another system or database.
  • To generate reports or analytics on recent orders.
  • To automate workflows that depend on order information, such as triggering shipment processes or notifications.

The node supports pagination, field selection, and sorting to tailor the results according to your needs.

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 (pagination size).
Fields Comma-separated list of specific fields to include in the response for each order.
Sorting Sorting criteria for the returned orders; e.g., "name" for ascending or "-name" for descending order.

Output

The output is a JSON array containing order objects retrieved from the Tripletex API. Each object represents an order with its associated fields as specified by the Fields input property or all fields if none are specified.

The node does not output binary data for this operation.

Example structure of one order item in the JSON output might include fields like:

{
  "id": 123,
  "orderDate": "2024-01-01T00:00:00Z",
  "deliveryDate": "2024-01-05T00:00:00Z",
  "customer": {
    "id": 456,
    "name": "Customer Name"
  },
  "orderLines": [
    {
      "productId": 789,
      "description": "Product description",
      "quantity": 2,
      "unitPrice": 100
    }
  ],
  "currency": "NOK"
}

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 credential's environment setting.
  • No additional external dependencies beyond HTTP requests to the Tripletex API.

Troubleshooting

  • Validation errors: If required parameters like orderDate or customerId are missing during create or update operations, the node will throw validation errors. For Get All, ensure numeric values for from and limit.
  • Authentication failures: Ensure the API key credential is correctly configured and has access to the Tripletex API.
  • Pagination issues: If you request too many records at once (exceeding API limits), the API may reject the request or truncate results. Use Limit to control batch size.
  • Invalid sorting or fields: Providing invalid field names or sorting criteria may result in API errors or empty responses. Verify field names against Tripletex API documentation.

Links and References

Discussion