Actions16
Overview
The "Get Reseller Orders" operation in the Order resource allows users to retrieve a list of orders associated with a specific reseller. This node is useful for scenarios where you need to monitor, report on, or process orders placed by resellers within a commerce platform. For example, a business might use this node to fetch all completed orders from a particular reseller over the last month to generate sales reports or trigger downstream workflows such as invoicing or fulfillment.
Properties
| Name | Meaning |
|---|---|
| Reseller ID | The unique identifier of the reseller whose orders you want to retrieve. This is a required field. |
| Return All | Boolean flag indicating whether to return all matching orders or limit the number of results. If set to false, the number of returned orders will be limited by the "Limit" property. |
| Limit | The maximum number of orders to return when "Return All" is false. The value must be at least 1 and no more than 500. |
| Filters | A collection of optional filters to narrow down the search results: |
| Status | Filter orders by their status. Possible values include Submitted, Processing, Error, Completed, and Cancelled. |
| Customer ID | Filter orders by the ID of the customer who placed the order. |
| Subscription ID | Filter orders by the subscription ID created from the order. |
| Created After | Filter orders created after a specified date/time. Supports either preset relative dates (e.g., Today, Yesterday, 1 Week Ago) or a custom date/time picker. |
| Created Before | Filter orders created before a specified date/time. Supports the same preset and custom date options as "Created After". |
Output
The output consists of an array of JSON objects, each representing an individual reseller order that matches the input criteria. Each JSON object contains detailed information about a single order, including its status, associated customer, subscription details, creation timestamps, and other relevant metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to the CloudBlue Commerce API or equivalent backend service that manages reseller orders.
- An API authentication token or API key credential must be configured in n8n to authorize requests.
- The node depends on a resource registry system internally to resolve and execute the requested resource-operation pair.
Troubleshooting
Common Issues:
- Invalid or missing Reseller ID will cause the node to fail because it is a required parameter.
- Exceeding the maximum allowed limit (more than 500) will likely result in an error or truncated results.
- Incorrect filter formats or unsupported filter values may cause the API to reject the request.
- Network or authentication errors if the API credentials are not properly configured or have expired.
Error Messages:
"Resource Order not found or not yet migrated": Indicates the node does not recognize the "order" resource, possibly due to misconfiguration or version mismatch."Unknown error occurred": Generic catch-all error; check API connectivity and credentials.- Errors related to item index indicate which input item caused failure, useful for debugging batch executions.
Resolutions:
- Ensure all required parameters are provided and valid.
- Verify API credentials and permissions.
- Use smaller limits or enable "Return All" cautiously to avoid timeouts.
- Review filter values for correctness and supported options.
Links and References
- CloudBlue Commerce API Documentation
- n8n Documentation on Creating Custom Nodes
- Date and Time Presets Explanation (for understanding preset date filters)