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 with the PickerPro service to interact with Mercado Libre data and services. It enables users to automate various tasks such as retrieving site listing types, market highlights, seller information, site categories, and more. Specifically, the "Site Listing Types" operation fetches the different types of listings available on a specified Mercado Libre site.

Common scenarios where this node is beneficial include:

  • Automating data retrieval about Mercado Libre marketplace structures.
  • Integrating Mercado Libre listing metadata into workflows for analytics or inventory management.
  • Enriching datasets with detailed listing type information for decision-making or reporting.

For example, using the "Site Listing Types" operation, a user can programmatically obtain all listing types for a given site ID, which can then be used to filter or categorize product listings in downstream processes.

Properties

Name Meaning
IntegrationToken The API token used to authenticate requests to the PickerPro Mercado Libre integration.
Site ID The identifier of the Mercado Libre site for which to retrieve listing types.

Output

The output JSON contains a single field named sitelistings which holds the data returned by the PickerPro API call for site listing types. This typically includes an array or object describing the various listing types available on the specified site.

Example output structure (simplified):

{
  "sitelistings": [
    {
      "id": "string",
      "name": "string",
      "description": "string"
    },
    ...
  ]
}

No binary data output is produced by this operation.

Dependencies

  • Requires an active PickerPro API key credential for authentication.
  • The node depends on the PickerPro API endpoints to fetch Mercado Libre data.
  • No additional environment variables are required beyond the API token input property.

Troubleshooting

  • Missing or invalid API token: The node will throw an error if the API key or organization ID is not configured properly. Ensure that the IntegrationToken property is correctly set.
  • Invalid or missing Site ID: If the Site ID is not provided or incorrect, the API call may fail or return empty results.
  • Unsupported operation error: If an unsupported operation name is passed, the node throws an error indicating the operation is not supported.
  • Network or API errors: Connectivity issues or API downtime can cause failures; verify network access and PickerPro service status.

Links and References

Discussion