Actions15
Overview
This node connects to the Tripletex API v2 and allows users to perform various operations on different resources such as customers, products, orders, inventory, invoices, and webhooks. Specifically, for the Product resource with the Get operation, it retrieves detailed information about a single product by its ID.
Typical use cases include:
- Fetching product details to display or process in workflows.
- Integrating product data from Tripletex into other systems.
- Automating inventory or sales processes that require up-to-date product information.
For example, a user might want to get the details of a specific product by providing its Product ID to enrich an order processing workflow with accurate product data.
Properties
| Name | Meaning |
|---|---|
| Product ID | The unique identifier of the product to retrieve. This is required for the Get, Update, and Delete operations on the Product resource. |
Output
The node outputs JSON data representing the product details retrieved from the Tripletex API. The structure corresponds directly to the API response for a product, typically including fields like product name, number (SKU), description, unit price, cost price, and currency.
No binary data output is produced by this operation.
Example output JSON snippet (structure depends on API response):
{
"id": "12345",
"name": "Sample Product",
"number": "SKU123",
"description": "A sample product description",
"unitPrice": 100,
"costPrice": 70,
"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 credential settings.
- No additional external dependencies are needed beyond HTTP access to the Tripletex API.
Troubleshooting
- Validation errors: If the Product ID is missing or empty when performing Get, Update, or Delete operations, the node will throw a validation error indicating the missing required field.
- Authentication failures: Ensure the API key credential is correctly configured and has appropriate permissions.
- API errors: The node forwards any API error messages received from Tripletex. Common issues include invalid product IDs or network connectivity problems.
- Rate limits: Be aware of any rate limiting imposed by the Tripletex API to avoid request rejections.
Links and References
- Tripletex API Documentation (official API docs for more details on product endpoints)
- n8n documentation on creating custom nodes