Actions15
Overview
This node integrates with the Tripletex API to create new orders in the system. It allows users to specify order details such as the order date, delivery date, customer information, currency, and detailed order lines including products, quantities, and prices. This node is useful for automating order creation workflows, syncing orders from other systems, or batch processing orders programmatically.
Practical examples include:
- Automatically creating an order when a customer completes a purchase on an e-commerce platform.
- Importing bulk orders from external databases or spreadsheets into Tripletex.
- Creating orders based on triggers from CRM or ERP systems to streamline sales operations.
Properties
| Name | Meaning |
|---|---|
| Currency | The currency code for the order (e.g., NOK). |
| Order Date | The date when the order was placed. This is required. |
| Delivery Date | The expected delivery date of the order. |
| Customer ID | The unique identifier of the customer placing the order. This is required. |
| Order Lines | A collection of line items in the order. Each line includes: |
| - Product ID: Identifier of the product (required). | |
| - Description: Optional description of the line item. | |
| - Quantity: Number of units ordered (required). | |
| - Unit Price: Price per unit of the product (required). |
Output
The node outputs JSON data representing the response from the Tripletex API after creating the order. This typically includes details of the newly created order such as its ID, status, and any metadata returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Tripletex API.
- The node uses the Tripletex API v2 endpoints.
- The base URL depends on the environment setting (production or test).
- Proper configuration of the API credentials within n8n is necessary.
Troubleshooting
- Validation errors: If required fields like "Order Date" or "Customer ID" are missing, the node will throw validation errors indicating which fields are required.
- Authentication failures: Errors related to invalid or missing API credentials can occur if the API key is not set up correctly.
- API errors: Any issues returned by the Tripletex API (e.g., invalid product IDs in order lines) will be surfaced in the node's error output.
- To handle errors gracefully, enable the "Continue On Fail" option in the node settings to allow workflow execution to proceed even if some executions fail.
Links and References
- Tripletex API Documentation (official API docs)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes