Tripletex

Connect to Tripletex API v2
Join our community

Actions15

Overview

This node connects to the Tripletex API v2 and allows users to manage customers, products, orders, inventory, invoices, and webhooks. Specifically, for the Customer - Get All operation, it retrieves a list of customers from the Tripletex system with support for pagination, field selection, and sorting.

Common scenarios where this node is beneficial include:

  • Synchronizing customer data from Tripletex into other systems.
  • Fetching customer lists for reporting or analysis.
  • Automating workflows that require bulk access to customer information.

For example, you could use this node to fetch all customers starting from index 0, limiting results to 100, returning only specific fields like name and email, sorted by name ascending or descending.

Properties

Name Meaning
From Starting index for pagination; defines the offset from which to start fetching customers.
Limit Maximum number of customer records to return in one request (pagination size).
Fields Comma-separated list of specific customer fields to return (e.g., "name,email").
Sorting Sorting criteria for the returned customers; prefix with "-" for descending order (e.g., "name" or "-name").

Output

The output is a JSON array containing customer objects as returned by the Tripletex API. Each object includes the customer data fields requested via the Fields property or all fields if none specified.

The structure corresponds directly to the Tripletex API's customer representation, including properties such as name, email, phone, address details, private person status, and organization number.

No binary data output is produced by this operation.

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 the configured environment setting.
  • Network connectivity to the Tripletex API endpoints is necessary.

Troubleshooting

  • Validation errors: If required parameters are missing (e.g., customer name when creating or updating), the node throws validation errors listing missing fields.
  • Authentication failures: Ensure the API key credential is correctly configured and has appropriate permissions.
  • Pagination issues: If From or Limit values are out of range or invalid, the API may return errors or empty results.
  • Unsupported operations: Attempting an unsupported operation-resource combination will result in an error indicating the unsupported action.
  • API rate limits or downtime: Handle API rate limits or service unavailability gracefully, possibly using the node's "Continue On Fail" option to avoid workflow interruption.

Links and References

Discussion