PickerPro Meli
Actions15
Overview
This node integrates PickerPro with n8n to automate various data retrieval tasks related to Mercado Libre, a popular e-commerce platform in Latin America. It enables users to fetch real-time information such as seller reputation, seller brands, market trends, site categories, and more by calling PickerPro's API endpoints.
For the Seller Reputation operation specifically, the node retrieves detailed reputation metrics for a given seller on Mercado Libre. This can be useful for sellers or buyers who want to assess the trustworthiness and performance of a seller before engaging in transactions.
Practical examples:
- An e-commerce manager automates monitoring of their own seller reputation to quickly react to changes.
- A buyer uses the node to verify the reputation of sellers before making purchases.
- Market analysts gather seller reputation data across multiple sellers to identify top performers.
Properties
| Name | Meaning |
|---|---|
| IntegrationToken | The secure token used to authenticate requests to the PickerPro API. |
| Seller ID | The unique identifier of the seller whose reputation information is being requested. |
Output
The node outputs a JSON object containing the seller's reputation data under the key sellerreputation. This data typically includes metrics such as ratings, sales history, customer feedback scores, and other relevant reputation indicators provided by PickerPro's API.
Example output structure (simplified):
{
"sellerreputation": {
"levelId": "5_green",
"powerSellerStatus": "platinum",
"metrics": {
"sales": 1234,
"cancellations": 12,
"claims": 3,
"delayedShipments": 1
},
"transactions": {
"completed": 1200,
"canceled": 15
}
}
}
No binary data output is produced by this operation.
Dependencies
- Requires an active PickerPro API credential with a valid API key and organization ID configured in n8n.
- The user must provide an integration token (
IntegrationToken) for authenticating individual API calls. - Network access to PickerPro's API endpoints is necessary.
Troubleshooting
- Missing API Key or Organization ID: The node will throw an error if these credentials are not configured properly. Ensure that the PickerPro API credential is set up correctly in n8n.
- Invalid or missing Integration Token: If the token parameter is empty or invalid, API calls will fail. Verify the token value.
- Unsupported Operation Error: If an unsupported operation name is provided, the node throws an error indicating the operation is not supported.
- Parameter Retrieval Errors: The node attempts to safely retrieve parameters but logs errors if any parameter is missing or malformed. Double-check all required input properties are provided.
- API Rate Limits or Network Issues: As with any external API call, network failures or rate limiting may cause errors. Implement retry logic or monitor API usage accordingly.