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 detailed information about sellers, market trends, site categories, and other marketplace data by calling PickerPro's API endpoints.

The Seller Brands operation specifically fetches the brands associated with a given seller on Mercado Libre. This can be useful for sellers or analysts who want to monitor brand portfolios, track competitor brands, or manage product listings more effectively.

Practical examples:

  • An e-commerce manager automates daily reports of all brands a particular seller offers.
  • A marketing analyst tracks changes in brand offerings from key sellers to adjust advertising strategies.
  • Inventory managers verify brand associations before updating stock or pricing.

Properties

Name Meaning
IntegrationToken The secret token used to authenticate requests to the PickerPro API.
Seller ID The unique identifier of the seller whose brands you want to retrieve.

Output

The node outputs a JSON object containing the seller's brands under the property sellerbrands. The structure is:

{
  "sellerbrands": { /* data returned by PickerPro API about seller's brands */ }
}

The exact structure depends on the PickerPro API response but typically includes brand names, IDs, and possibly additional metadata related to each brand.

No binary data output is produced by this operation.

Dependencies

  • Requires an active PickerPro API credential configured in n8n, which must include an API key and organization ID.
  • The user must provide a valid integration token (IntegrationToken) as part of the node parameters.
  • Relies on PickerPro's external API services to fetch Mercado Libre data.

Troubleshooting

  • Missing API Key or Organization ID: The node will throw an error if these credentials are not set up properly. Ensure that the PickerPro API credential is correctly configured in n8n.
  • Invalid or missing Integration Token: If the token parameter is empty or incorrect, API calls will fail. Verify the token value.
  • Unsupported Operation Error: If the operation parameter is set to a value not supported by the node, an error will be thrown.
  • Network or API errors: Since the node depends on external API calls, network issues or API downtime may cause failures. Check connectivity and PickerPro service status.
  • Incorrect Seller ID: Providing an invalid or non-existent seller ID will likely result in empty or error responses from the API.

Links and References

Discussion