Rvops

Overview

This node integrates with the Rvops platform to manage products and other CRM-related resources. Specifically, for the "Produto" (Product) resource with the "List Products" operation, it retrieves a list of products from the Rvops system. It supports pagination, sorting, and filtering options, and can either fetch a limited number of products or all available products at once.

Common scenarios where this node is beneficial include:

• Synchronizing product data from Rvops into another system.
• Automating workflows that require up-to-date product lists.
• Monitoring new or updated products by using cursor-based incremental fetching.

For example, you might use this node to regularly pull the latest products sorted by their last update date, then trigger further processing such as inventory updates or marketing campaigns.

Properties

Name	Meaning
Autenticação Do Cliente	Authentication method; currently supports "Access Token".
Limite	Limits the number of products returned in one execution (1 to 100).
Listar Todos	Boolean flag indicating whether to retrieve all products at once (ignores the limit if true).
Monitorar Novos Valores	Boolean flag to enable watching for new or updated products since the last run using a cursor.
Campo De Ordenação	Field to sort the product list by; options are "Data De Modificação" (updatedAt) or "Data De Inclusão" (createdAt).
Tipo De Ordenação	Sort order type; options are "Ascendente" (ascending) or "Descendente" (descending).

Note: Some properties like sorting fields and order types have display conditions based on whether monitoring is enabled.

Output

The node outputs an array of product objects under the json field. Each product object includes:

• id: Unique identifier of the product.
• properties: An object containing product details such as name, price, SKU, frequency, unit cost, URL, months term, description, and timestamps (updatedAt, createdAt).

The output is structured so each item corresponds to one product, suitable for downstream nodes to process individually.

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential for authentication (referred generically as an API access token).
• The node uses the Rvops REST API endpoints to perform operations.
• No additional external services or environment variables are required beyond the configured API credentials.

Troubleshooting

• Common issues:

  • Invalid or expired API token will cause authentication failures.
  • Exceeding the maximum allowed limit (over 100) will likely result in an error.
  • Network connectivity issues may cause request timeouts or failures.
  • Using the watch option without proper cursor management could lead to missing or duplicated data.

• Error messages:

  • Errors returned from the API include HTTP status codes and server messages, which the node surfaces in the output when "Continue On Fail" is enabled.
  • Typical errors include 401 Unauthorized (invalid token), 400 Bad Request (invalid parameters), and 429 Too Many Requests (rate limiting).

• Resolutions:

  • Verify and refresh the API token if authentication fails.
  • Ensure limits are within allowed ranges.
  • Check network connectivity and retry failed requests.
  • Use the watch feature carefully and understand how cursors are stored between executions.

Links and References

• Rvops API Documentation (Assumed link, replace with actual if known)
• n8n documentation on Creating Custom Nodes
• General REST API best practices for pagination and authentication.

---

This summary focuses exclusively on the "Produto" resource and its "List Products" operation as requested.