Actions15
Overview
This node connects to the Tripletex API v2 and allows you to manage customers, products, orders, inventory, invoices, and webhooks. Specifically, for the Customer - Get operation, it retrieves detailed information about a customer by their unique ID.
Common scenarios where this node is beneficial include:
- Fetching customer details to display or process in workflows.
- Integrating Tripletex customer data into other systems or automations.
- Validating customer existence before performing further operations like creating orders.
Practical example:
- You have an order processing workflow that needs to enrich order data with customer contact info from Tripletex. Using this node’s "Get Customer" operation, you can fetch the customer details by ID and use them downstream.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer to retrieve. This is required for the Get operation on the Customer resource. |
Output
The node outputs JSON data representing the customer object retrieved from the Tripletex API. The structure corresponds to the customer details as returned by the API endpoint /v2/customer/{customerId}. It typically includes fields such as name, email, phone, address, whether the customer is a private person, organization number, and other relevant customer attributes.
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 a test environment and production based on the configured environment setting in credentials.
- HTTP requests are made with standard JSON content-type headers and Basic Authentication using a session token generated from the API key.
Troubleshooting
- Validation errors: If the Customer ID is missing or empty when performing the Get operation, the node will throw a validation error indicating the missing required parameter.
- Authentication failures: Errors related to invalid or expired API keys or tokens may occur. Ensure the API key credential is correctly configured and has necessary permissions.
- Not found errors: If the specified Customer ID does not exist in Tripletex, the API will return an error which the node passes through. Verify the ID is correct.
- Network issues: Connectivity problems to the Tripletex API endpoints can cause request failures. Check network access and API availability.
Links and References
- Tripletex API Documentation (official API docs)
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)