Actions16
Overview
This node enables creating new orders within a commerce platform by specifying customer and product details. It is useful in scenarios where automated order placement is needed, such as integrating e-commerce systems with inventory or billing platforms, or automating bulk order creation from external data sources.
For example, you can use this node to:
- Automatically create an order when a customer completes a checkout process on a website.
- Generate orders based on subscription renewals or usage triggers.
- Batch import orders from CSV or other data feeds into the commerce system.
Properties
| Name | Meaning |
|---|---|
| Order Data | Collection of values required to create an order. |
| Customer ID | The unique identifier of the customer placing the order. |
| Products | List of products included in the order. |
| MPN | Manufacturer Part Number identifying each product. |
| Quantity | Number of units for each product in the order. |
The "Order Data" property is a fixed collection that requires specifying the "Customer ID" and one or more "Products". Each product entry must include its MPN and quantity.
Output
The node outputs JSON objects representing the created order(s). Each output item contains the full details of the newly created order as returned by the commerce platform's API.
No binary data output is produced by this node.
Dependencies
- Requires an initialized API service client configured with appropriate credentials (e.g., an API key or authentication token) to communicate with the commerce platform.
- The node depends on a resource registry system that manages available resources and their operations.
- Proper configuration of the API credentials in n8n is necessary for successful execution.
Troubleshooting
- Resource Not Found Error: If the specified resource ("order") is not recognized, ensure the node and its dependencies are correctly installed and up to date.
- API Authentication Failures: Verify that the API credentials are valid and have sufficient permissions to create orders.
- Validation Errors: Missing required fields like Customer ID or product details will cause errors. Double-check input data completeness.
- Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if some fail, returning error messages in the output JSON.
Links and References
- Refer to your commerce platform’s API documentation for detailed information about order creation endpoints and required fields.
- Consult n8n documentation on how to configure API credentials and handle fixed collections in node parameters.