Actions11
Overview
The node is designed to update shipment records in the CoreSense system. It allows users to modify various shipment-related fields such as cancellation status, closure status, customer deadlines, shipping dates, and pricing. This node is useful in scenarios where shipment details need to be programmatically updated based on workflow logic, for example, updating a shipment's status after receiving new information from a fulfillment center or adjusting shipping prices dynamically.
Practical examples include:
- Automatically marking shipments as cancelled or closed based on external triggers.
- Updating customer deadlines or requested ship dates when changes occur.
- Adjusting shipping prices before finalizing an order shipment.
Properties
| Name | Meaning |
|---|---|
| Automatically Map | Whether to allow the system to automatically map input fields to API fields by matching names. |
| Cancelled | Whether the shipment/order is cancelled (boolean). |
| Closed | Whether the shipment/order is closed (boolean). |
| Customer Deadline | The deadline date/time for customer fulfillment (string). |
| Customer ID | The numeric ID of the customer to assign this shipment/order to (not contact ID). |
| Delayed Ship Date | The requested ship date for customer fulfillment (string). |
| Shipment ID | The unique numeric identifier of the shipment/order to update (required). |
| Shipping Price | Optional price charged for shipping for the order (number). |
Note: When "Automatically Map" is enabled, the node attempts to match input fields to API fields automatically, so individual fields like Cancelled, Closed, etc., are not manually set.
Output
The node outputs JSON data representing the updated shipment record as returned by the CoreSense API. This typically includes confirmation of the updated fields and any metadata related to the shipment update operation.
If binary data were involved (e.g., documents or labels), it would be summarized here, but this node focuses on JSON shipment 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 and action modules specific to CoreSense integration.
- No additional external services beyond CoreSense API are required.
Troubleshooting
Common Issues:
- Missing or invalid Shipment ID will cause the update to fail.
- Incorrect field names or types when "Automatically Map" is disabled may result in API errors.
- Network or authentication failures with the CoreSense API can prevent updates.
Error Messages:
- Errors indicating missing required fields (e.g., Shipment ID) should be resolved by providing those fields.
- Authentication errors require verifying the API key credential setup.
- Validation errors from the API usually mean some input fields have invalid values or formats; double-check the property inputs.
Links and References
- CoreSense API documentation (refer to your CoreSense API docs for detailed field definitions and update operations).
- n8n documentation on creating and using custom nodes and credentials.