Rvops

Overview

This node integrates with the Rvops platform to perform operations on various resources, including products. Specifically, for the "Produto" (Product) resource and the "Search a Product" operation, it allows users to search for products based on customizable filters and retrieve selected product properties. This is useful in scenarios where you want to query your product catalog dynamically, filter products by specific criteria (e.g., price, SKU, description), and use the results downstream in your workflow.

Practical examples include:

• Searching for products within a certain price range.
• Filtering products by SKU or name containing specific keywords.
• Retrieving product details updated after a certain date.
• Listing all products matching complex filter conditions.

Properties

Name	Meaning
Autenticação Do Cliente	Authentication method to access the API; currently supports "Access Token".
Campo De Ordenação	Field to sort the search results by. Options include: "Data De Modificação" (date_modified) and "Data De Inclusão" (date_added). Default is "date_modified".
Tipo De Ordenação	Sort order type. Options are "Ascendente" (ascending) and "Descendente" (descending). Default is ascending.
Filtros	Filters to apply to the product search. Each filter includes: - Propriedade (property): e.g., ID, Nome, Preço, SKU, Frequência, Custo Unitário, URL, Prazo Em Meses, Descrição, Data E Hora Da Última Atualização. - Operador (operator): e.g., Igual A (EQ), Diferente De (NEQ), Maior Que (GT), Menor Que (LT), Contém a Palavra Específica (CONTAINS_TOKEN), etc. - Valor a Filtrar (value): string value to filter by.
Propriedades	Additional product properties to include in the search result. Options correspond to product fields like ID, Nome, Preço, SKU, etc.
Limit	Maximum number of products to return in the search. Integer between 1 and 100. Default is 100.
Listar Todos	Boolean flag indicating whether to list all matching products at once (true) or limit the results to the specified limit (false).

Output

The node outputs an array of JSON objects representing the products found by the search. Each product object contains:

• id: The unique identifier of the product.
• properties: An object containing the requested product properties as key-value pairs, such as name, price, SKU, description, etc.

No binary data output is produced by this operation.

Example output JSON snippet:

[
  {
    "id": "123",
    "properties": {
      "name": "Product A",
      "price": 29.99,
      "sku": "SKU123",
      "description": "Description of Product A",
      "updatedAt": "2024-01-15T12:00:00Z"
    }
  },
  {
    "id": "456",
    "properties": {
      "name": "Product B",
      "price": 49.99,
      "sku": "SKU456",
      "description": "Description of Product B",
      "updatedAt": "2024-02-10T08:30:00Z"
    }
  }
]

Dependencies

• Requires an API authentication token (access token) configured in n8n credentials to authenticate requests to the Rvops API.
• Relies on the internal helper function to make HTTP requests (elozApiRequest).
• No additional external dependencies beyond the Rvops API and proper credential setup.

Troubleshooting

• Common issues:

  • Invalid or missing API token will cause authentication errors.
  • Using unsupported filter operators or invalid property names may result in API errors.
  • Requesting more than the allowed limit (over 100) will be rejected.
  • Network connectivity issues can cause request failures.

• Error messages:

  • Authentication errors typically indicate invalid or expired tokens; refresh or reconfigure credentials.
  • Validation errors from the API about filters or properties suggest checking the input parameters for correctness.
  • Rate limiting or server errors should be retried after some delay.

• Resolution tips:

  • Verify that the access token is correctly set up in n8n credentials.
  • Double-check filter property names and operators against the supported list.
  • Use the "Listar Todos" option carefully to avoid large data loads that might time out.
  • Enable "Continue On Fail" in the node settings to handle partial failures gracefully.

Links and References

• Rvops API Documentation (hypothetical link, replace with actual if available)
• n8n documentation on Creating Custom Nodes
• General REST API best practices for filtering and pagination

---

This summary focuses exclusively on the "Produto" resource and the "Search a Product" operation as requested.