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
Join our community

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 retrieve real-time data such as seller information, market trends, site categories, and more by calling PickerPro's API endpoints.

Common scenarios where this node is beneficial include:

  • Synchronizing order and stock data between Mercado Libre and other systems.
  • Monitoring seller reputation and brand information.
  • Analyzing market highlights and trends for strategic decisions.
  • Fetching detailed site category or listing information to optimize product listings.

For example, a user can use the "Seller Info" operation to fetch detailed information about their Mercado Libre seller account using an integration token, enabling automated reporting or alerts within their workflow.

Properties

Name Meaning
IntegrationToken The secret token used to authenticate requests to the PickerPro API for Mercado Libre.

Note: Although the full node supports many operations and properties, for the Default resource and Seller Info operation, only the IntegrationToken property is relevant.

Output

The output JSON contains a single field named sellerinfo, which holds the data returned from the PickerPro API about the seller's information on Mercado Libre.

Example output structure (simplified):

{
  "sellerinfo": {
    // Seller details as returned by PickerPro API
  }
}

No binary data output is produced by this operation.

Dependencies

  • Requires an active PickerPro API key credential configured in n8n.
  • Requires an organization ID associated with the PickerPro account.
  • The user must provide a valid Integration Token string parameter (token) for authenticating API calls.

Troubleshooting

  • Missing API Key or Organization ID: The node throws an error if these credentials are not configured properly. Ensure that the PickerPro API key and organization ID are set up in n8n credentials.
  • Invalid or missing Integration Token: If the IntegrationToken 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 will throw an error indicating the operation is not supported.
  • Parameter retrieval errors: The node attempts to safely get parameters like siteId, query, etc., but logs errors if they are missing or invalid. For the Seller Info operation, these are not required.

Links and References

Discussion