Actions4
- Order Actions
- Return Actions
Overview
This node integrates with the OTTO Market API to manage return items. Specifically, the "Return" resource with the "List" operation fetches a paginated list of return items filtered by their status. This is useful for scenarios where you want to monitor or process returns based on their current state, such as accepted returns ready for further handling or rejected returns requiring attention.
Practical examples include:
- Automatically retrieving all accepted returns daily to initiate refund processes.
- Listing rejected returns to analyze common issues or customer complaints.
- Fetching announced or misdirected returns for logistics follow-up.
Properties
| Name | Meaning |
|---|---|
| Status | The return status to filter the listed return items by. Options: ACCEPTED, REJECTED, ANNOUNCED, MISDIRECTED |
Output
The output JSON contains an array of objects under the key positionItems. Each object represents a return item matching the specified status. The structure corresponds to the OTTO Market API's return item schema, including details about each return position.
No binary data output is produced by this operation.
Example output snippet (simplified):
[
{
"positionItems": [
{
"returnId": "12345",
"status": "ACCEPTED",
"orderId": "98765",
"productDetails": { /* ... */ },
"quantity": 1,
"reason": "Damaged item"
},
...
]
}
]
Dependencies
- Requires an active connection to the OTTO Market API using a valid API authentication token configured in n8n credentials.
- The node depends on the OTTO Market API being accessible and the user having appropriate permissions to query return data.
Troubleshooting
Common Issues:
- Invalid or expired API credentials will cause authentication failures.
- Requesting returns with a status that does not exist or has no data may return empty results.
- Network connectivity problems can prevent successful API calls.
Error Messages:
- Authentication errors typically indicate invalid API keys; verify and update credentials.
- HTTP 4xx or 5xx errors from the API suggest issues with request parameters or server availability; check the status parameter and API status.
- Timeout errors may require increasing timeout settings or checking network stability.
Links and References
- OTTO Market API Documentation – Official API docs for detailed endpoint information and usage guidelines.