Actions12
Overview
The node integrates with the Shipentegra API to manage shipping and logistics operations. Specifically, the "Find Orders" operation allows users to search for orders within their Shipentegra account based on various criteria such as page number, limit per page, order status, order number, and store ID.
This operation is beneficial in scenarios where you need to retrieve a list of orders for processing, reporting, or synchronization with other systems. For example, an e-commerce platform could use this node to fetch recent orders to initiate shipping workflows or update order statuses.
Properties
| Name | Meaning |
|---|---|
| Page | The page number of results to retrieve (minimum 1). |
| Limit | The maximum number of orders to return per page (between 20 and 100). |
| Status | Filter orders by their status. Options: None (no filter), 0, 1, 2, 3, 4, 5 (status codes). |
| Order Number | Filter orders by a specific order number (string). |
| Store ID | Filter orders by a specific store identifier (number). |
Output
The output contains JSON data representing the list of orders retrieved from the Shipentegra API according to the specified filters. Each item in the output corresponds to an order object with details such as order number, status, store ID, and other relevant order information.
The node does not explicitly mention binary data output for this operation.
Dependencies
- Requires an API key credential for authenticating with the Shipentegra API.
- The base URL for API requests is
https://publicapi.shipentegra.com/v1. - Requests are made with JSON content type and accept headers.
- The node expects the user to configure the API authentication credentials properly in n8n.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Providing invalid values for properties like page number or limit may result in errors or empty responses.
- Filtering by non-existent order numbers or store IDs will return no results.
- Error messages:
- Authentication errors typically indicate incorrect or expired API keys; verify and update credentials.
- Validation errors may occur if property values are out of allowed ranges; ensure page ≥ 1 and limit between 20 and 100.
- Network or API downtime can cause request failures; check connectivity and Shipentegra service status.
Links and References
- Shipentegra API Documentation (general reference for API endpoints and parameters)
- n8n documentation on creating custom nodes for further customization guidance