PickerPro Meli icon

PickerPro Meli

This node integrates PickerPro with n8n to automate management in Mercado Libre, allowing order synchronization, stock updates and warehouse consultation in real time

Overview

This node integrates PickerPro with n8n to automate various data retrieval and management tasks related to Mercado Libre, a popular e-commerce platform in Latin America. It enables users to fetch market trends, market highlights, seller information, site categories, and other marketplace insights by calling PickerPro's API endpoints.

A common use case is for e-commerce managers or analysts who want to monitor market trends or seller reputations automatically within their workflows. For example, a user can set up this node to regularly pull "Market Trends" data for a specific category to analyze product demand changes over time or retrieve "Market Highlights" to identify trending products.

Properties

Name Meaning
IntegrationToken The secure token used to authenticate requests to the PickerPro API.
Category ID The identifier of the product category for which to retrieve market trends or highlights.

Note: These properties are specifically relevant when using the "Market Trends" operation.

Output

The node outputs JSON data under the field markettrends when the "Market Trends" operation is selected. This JSON contains detailed information about market trends for the specified category, such as sales volume, price changes, or other relevant metrics provided by PickerPro.

The output structure is an array containing one object with a json property, for example:

[
  {
    "json": {
      "markettrends": { /* Market trends data for the given category */ }
    }
  }
]

No binary data output is produced by this operation.

Dependencies

  • Requires an active PickerPro API integration with valid credentials (an API key and organization ID).
  • The node expects the user to provide an integration token (IntegrationToken) for authenticating API calls.
  • No additional environment variables or external services beyond PickerPro's API are required.

Troubleshooting

  • Missing Credentials: If the API key or organization ID is not configured properly, the node will throw an error stating "API Key or Organization ID not configured." Ensure that the PickerPro API credentials are correctly set up in n8n.
  • Invalid Operation: Selecting an unsupported operation will result in an error message like "Operation not supported: [operationName]". Verify that the operation name matches one of the supported options.
  • Parameter Errors: If required parameters such as Category ID or IntegrationToken are missing or empty, the node may fail or return incomplete data. Double-check that all required inputs are provided.
  • API Errors: Network issues or invalid tokens can cause API request failures. Check your network connectivity and confirm that the integration token is valid and has necessary permissions.

Links and References

Discussion