Actions11
Overview
This node integrates with the CoreSense system to update existing orders. It allows users to modify various order attributes such as cancellation status, closure status, customer deadlines, shipping dates, and customer assignment. This is useful in scenarios where order details need to be adjusted after creation, for example, updating a delivery deadline, marking an order as cancelled, or changing the assigned customer.
Practical examples:
- Marking an order as cancelled if the customer decides not to proceed.
- Updating the requested ship date to accommodate changes in logistics.
- Assigning the order to a different customer ID due to administrative corrections.
Properties
| Name | Meaning |
|---|---|
| Automatically Map | Whether to allow the system to automatically map input fields based on matching API fields. |
| Cancelled | Whether the order is cancelled (boolean). |
| Closed | Whether the order is closed (boolean). |
| Customer Deadline | The deadline for customer fulfillment (string, e.g., date/time). |
| Customer ID | The customer ID to assign this order (number). |
| Delayed Ship Date | The requested ship date for customer fulfillment (string, e.g., date/time). |
| Order ID | The unique identifier of the order to update (required number). |
Note: When "Automatically Map" is enabled, the system attempts to determine the contents based on field names that must match the API fields. If disabled, the user manually specifies the above properties.
Output
The node outputs JSON data representing the updated order information as returned by the CoreSense API. This typically includes confirmation of the updated fields and possibly the full updated order record.
If binary data were involved (e.g., attachments), it would be summarized here, but this node focuses on JSON order data only.
Dependencies
- Requires an active connection to the CoreSense API via an API key credential configured in n8n.
- The node depends on internal routing logic and helper methods bundled within the node's source code to handle API requests.
- No additional external services beyond CoreSense are required.
Troubleshooting
Common issues:
- Incorrect or missing Order ID will cause the update to fail.
- Enabling "Automatically Map" requires that input field names exactly match the CoreSense API field names; mismatches can lead to incomplete or failed updates.
- Invalid date formats for "Customer Deadline" or "Delayed Ship Date" may cause errors.
- Network or authentication failures with the CoreSense API.
Error messages:
- "Order ID is required": Ensure the Order ID property is set.
- "Invalid field mapping": Check that field names match API expectations when using automatic mapping.
- Authentication errors: Verify the API key credential is correctly configured and has necessary permissions.
- API response errors: Review error details from CoreSense API for specific causes.
Links and References
- CoreSense API documentation (refer to official CoreSense developer resources for detailed API field definitions and update operations).
- n8n documentation on creating and configuring API credentials.
- Best practices for date/time formatting in API requests.