Actions11
Overview
This node integrates with the CoreSense system to create new orders. It allows users to specify detailed order information such as customer ID, channel, billing contact, shipping costs, payment details, and products included in the order. The node supports an "Automatically Map" option that lets the system infer order contents based on matching field names, simplifying data input when the source data aligns with the API fields.
Common scenarios for this node include automating order creation from e-commerce platforms, syncing orders from external sales channels, or programmatically generating orders based on business logic workflows. For example, a user could automate creating an order whenever a new customer signs up or when a payment is received.
Properties
| Name | Meaning |
|---|---|
| Automatically Map | Whether to allow the system to determine the order contents automatically by matching field names (must match API fields). Boolean: true or false. |
| Customer ID | The numeric ID of the customer to assign this order to. Required if automatic mapping is disabled. |
| Channel Name or ID | The originating sales channel for the order. Choose from a predefined list or specify an ID via expression. |
| Billing Contact ID | (Optional) Numeric ID of the billing contact if different from the default. |
| Shipping Price | (Optional) Numeric value representing the price charged for shipping. |
| Payment Receivable Type ID | (Optional) Numeric ID indicating the type of payment receivable; if provided, a payment will be created. |
| Shipping Tax | (Optional) Numeric amount of tax applied over the shipping cost. |
| Shipping Tax Rate | (Optional) Numeric tax rate; if provided, it overrides the shipping tax with a calculated value. |
| Products | A string representing the list of products included in the order. |
Output
The node outputs JSON data representing the newly created order record as returned by the CoreSense API. This typically includes order identifiers, status, timestamps, and any other metadata provided by the API response. The output does not explicitly mention binary data, so it is assumed to be purely JSON structured.
Dependencies
- Requires an active connection to the CoreSense API using an API key or authentication token configured in n8n credentials.
- The node depends on internal methods and routers defined in the bundled source code to handle API communication and data processing.
- The "Channel Name or ID" property loads options dynamically via a method named
getChannels, which likely queries available channels from CoreSense.
Troubleshooting
- Missing required fields: If "Automatically Map" is false, ensure that "Customer ID" and "Channel Name or ID" are provided; otherwise, the API call may fail.
- Invalid IDs: Providing incorrect numeric IDs for customer, billing contact, or payment receivable type can cause errors from the API.
- Automatic mapping mismatches: When using automatic mapping, field names in the input data must exactly match the API's expected field names; otherwise, the order creation may fail or produce incomplete data.
- API authentication errors: Ensure the API key or authentication token is correctly configured in n8n credentials to avoid authorization failures.
- Dynamic options loading failure: If the channel list fails to load, verify network connectivity and API availability.
Links and References
- CoreSense API Documentation (hypothetical link)
- n8n Expressions Documentation - for using expressions in properties like Channel ID
- n8n Node Development Guide