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. This is useful for scenarios where you want to fetch multiple customer records for reporting, synchronization with other systems, or bulk processing.
For example, you might use this node to:
- Retrieve all customers starting from a specific index for pagination.
- Limit the number of customers returned in one request.
- Select specific fields to optimize data transfer.
- Sort the results by a particular field in ascending or descending order.
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 the response. |
| Fields | Comma-separated list of specific customer fields to include in the response (e.g., "name,email"). |
| Sorting | Sorting criteria for the results; prefix with "-" for descending order (e.g., "name" or "-name"). |
Output
The output is a JSON object containing the retrieved customer data as returned by the Tripletex API. The structure depends on the API response but typically includes an array of customer objects with their respective fields.
json: Contains the customer data fetched from the API.binary: Empty in this operation since no binary data is returned.
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 like "Customer name" are missing during create or update operations, the node will throw validation errors. For "Get All", ensure numeric values for "From" and "Limit" are valid.
- Authentication errors: Ensure that the API key credential is correctly configured and has access to the Tripletex API.
- API rate limits or connectivity issues: Network problems or API limits may cause request failures. Check network connectivity and API usage quotas.
- Unsupported operation error: Occurs if an invalid resource-operation combination is selected.
Links and References
- Tripletex API Documentation (official API docs)
- n8n HTTP Request Node documentation for understanding how requests are made within n8n workflows