PickerPro Meli
Actions15
Overview
This node integrates PickerPro with n8n to automate various management tasks related to Mercado Libre, a popular e-commerce platform in Latin America. It enables users to synchronize orders, update stock levels, and consult warehouse information in real time by leveraging PickerPro's API.
The node supports multiple operations that provide detailed market data, seller information, site-specific categories, listing types, prices, exposures, and search capabilities. For the "Site Listing Types Info" operation specifically, it retrieves detailed information about a particular listing type on a specified site.
Practical examples:
- Automatically fetch detailed info about a specific listing type on a Mercado Libre site to adjust your inventory or pricing strategy.
- Retrieve site categories or seller reputation data to enhance marketplace analytics workflows.
- Use site search functionality to find listings matching certain queries programmatically.
Properties
| Name | Meaning |
|---|---|
| IntegrationToken | The token used to authenticate requests to PickerPro's API. |
| Site ID | Identifier of the Mercado Libre site for which data is requested (e.g., "MLA" for Argentina). |
| Listing Type ID | Identifier of the listing type to retrieve detailed information about (used in "Site Listing Types Info" operation). |
Output
The output JSON structure depends on the selected operation. For the "Site Listing Types Info" operation, the output contains a field named sitelistingsinfo which holds the detailed information about the specified listing type on the given site.
Example output structure snippet:
{
"sitelistingsinfo": {
/* Detailed info about the listing type */
}
}
The node does not output binary data; all outputs are JSON objects containing the requested data from PickerPro/Mercado Libre APIs.
Dependencies
- Requires an active PickerPro API key credential for authentication.
- The node internally calls various PickerPro API endpoints corresponding to Mercado Libre data.
- No additional environment variables or external services are required beyond the provided API token.
Troubleshooting
- Missing API Key or Organization ID: The node throws an error if the API key or organization ID is not configured properly. Ensure these credentials are set up correctly in n8n.
- Invalid or missing parameters: Required parameters such as
token,siteId, orlistingTypeIdmust be provided depending on the operation. Missing these will cause errors. - Unsupported operation: If an unsupported operation name is provided, the node will throw an error indicating the operation is not supported.
- API request failures: Network issues or invalid tokens may cause API calls to fail. Verify network connectivity and token validity.
- Parameter retrieval errors: The node logs errors when failing to get optional parameters but continues execution; ensure parameters are correctly named and provided.