Actions12
Overview
The node integrates with the Shipentegra API to manage shipping and logistics operations. Specifically, the "Create Post Orders" operation allows users to create post orders by submitting one or more order IDs to the Shipentegra system. This is useful in scenarios where you want to automate the creation of shipping orders for fulfillment after receiving order information from an e-commerce platform or ERP system.
Practical examples include:
- Automatically creating shipping orders in Shipentegra when new sales orders are received.
- Batch processing multiple order IDs to generate corresponding post orders in a single workflow.
- Optionally toggling a boolean flag (named "Shipentegra") that might control additional behavior during order creation.
Properties
| Name | Meaning |
|---|---|
| Order IDs | A collection of one or more numeric order IDs to be created as post orders. Each ID must be between 1 and 9007199254740991. |
| Shipentegra | A boolean flag (true/false) that may modify the behavior of the post order creation process. |
Output
The node outputs JSON data representing the response from the Shipentegra API after attempting to create the post orders. The structure typically includes details about the created orders, status messages, or error information if the request failed.
If the node supports binary data output (not explicitly shown here), it would represent files such as shipping labels or documents related to the orders.
Dependencies
- Requires an API key credential for authenticating with the Shipentegra API.
- The base URL for API requests is
https://publicapi.shipentegra.com/v1. - The node expects JSON content type and accepts JSON responses.
- Language preference can be set via credentials but defaults to English (
en-US).
Troubleshooting
- Common issues:
- Invalid or missing order IDs will cause the API request to fail.
- Authentication errors if the API key credential is not configured correctly.
- Network connectivity problems preventing access to the Shipentegra API endpoint.
- Error messages:
- Errors returned from the API will be included in the node's output; these should be reviewed to understand specific failure reasons.
- If the node fails due to missing required properties (e.g., no order IDs provided), ensure all mandatory fields are filled.
- Resolutions:
- Verify that all order IDs are valid numbers within the allowed range.
- Confirm that the API key credential is properly set up in n8n.
- Check network settings and firewall rules to allow outbound requests to the Shipentegra API.
Links and References
- Shipentegra API Documentation (assumed base URL for reference)
- n8n documentation on creating custom nodes