PickerPro
Actions2
Overview
This node integrates with the PickerPro platform to automate e-commerce operations such as managing warehouses, zones within warehouses, stock inventories by zone, and marketplace integrations. It is useful for workflows that require centralized control over multiple sales channels, inventory tracking, and warehouse management.
The Get Zones operation specifically retrieves all zones associated with a given warehouse. This can help users organize inventory locations, optimize picking routes, or analyze stock distribution within a warehouse.
Practical example:
A logistics manager wants to fetch all zones in a specific warehouse to update their internal system with current zone configurations or to prepare for an inventory audit.
Properties
| Name | Meaning |
|---|---|
| Warehouse ID | The unique identifier of the warehouse for which zones should be retrieved. |
Output
The output JSON contains a single field:
zones: An array representing the zones within the specified warehouse. Each element corresponds to a zone object as returned by the PickerPro API.
Example output structure:
{
"zones": [
{
"id": "zone1",
"name": "Zone A",
"description": "Cold storage area"
// other zone-specific fields
},
{
"id": "zone2",
"name": "Zone B",
"description": "General storage"
}
]
}
No binary data output is produced by this operation.
Dependencies
- Requires an active PickerPro API key credential and organization ID configured in n8n.
- Relies on PickerPro's REST API endpoints to fetch zone data.
- The node uses internal helper functions from a bundled core API module to perform HTTP requests.
Troubleshooting
- Missing API Key or Organization ID: The node will throw an error if these credentials are not set up properly. Ensure you have configured the required API authentication details in n8n credentials.
- Invalid Warehouse ID: If the provided warehouse ID does not exist or is incorrect, the API may return an empty list or an error. Verify the warehouse ID before running the node.
- Network or API Errors: Connectivity issues or PickerPro service downtime can cause failures. Check network access and PickerPro service status.
- Operation Not Supported Error: Occurs if an unsupported operation value is passed. Confirm the operation parameter is set to "getZones" for this use case.
Links and References
- PickerPro Official Website (for general product info)
- PickerPro API documentation (refer to your PickerPro account or support for API docs)