Tripletex

Connect to Tripletex API v2
Join our community

Actions15

Overview

This node connects to the Tripletex API v2 and allows you to interact with various resources such as customers, products, and orders. Specifically, for the Product resource with the Get All operation, it retrieves a list of products from your Tripletex account.

Common scenarios where this node is beneficial include:

  • Synchronizing product data from Tripletex into other systems or databases.
  • Automating inventory or catalog updates by fetching all products regularly.
  • Generating reports or analytics based on the full product list.

For example, you could use this node to fetch all products starting from a certain index (pagination), limit the number of results returned, select specific fields to reduce payload size, or sort the products by name or other criteria.

Properties

Name Meaning
From Starting index for pagination. Defines the offset from which to start retrieving products.
Limit Maximum number of products to return in one request.
Fields Comma-separated list of product fields to return. Allows selecting only needed data fields.
Sorting Sorting criteria for the results. For example, "name" for ascending or "-name" for descending order.

Output

The output is a JSON array containing product objects retrieved from the Tripletex API. Each object represents a product with its properties as defined by the API response, potentially filtered by the selected fields.

The node does not output binary data for this operation.

Example structure of each product item in the JSON output might include fields like:

{
  "id": 123,
  "name": "Product Name",
  "number": "SKU123",
  "description": "Product description",
  "unitPrice": 100.0,
  "costPrice": 80.0,
  "currency": "NOK"
}

Dependencies

  • Requires an API key credential for authenticating with the Tripletex API.
  • The node uses the Tripletex API base URL, which can be configured for either production or test environments via credentials.
  • No additional external dependencies are required beyond the HTTP request helper provided by n8n.

Troubleshooting

  • Validation errors: If required parameters are missing or invalid, the node will throw validation errors such as "Product name is required" when creating or updating products.
  • Authentication failures: Ensure that the API key credential is correctly set up and has appropriate permissions.
  • Pagination issues: If you request too many items at once, the API may limit the response. Use the "From" and "Limit" properties to paginate through results.
  • Field filtering: Providing incorrect field names in the "Fields" property may result in empty or partial responses.
  • Sorting syntax: Incorrect sorting strings may cause the API to ignore the parameter or return errors; use the format "fieldName" or "-fieldName".

Links and References

Discussion