Rvops

Overview

This node integrates with the Rvops platform to manage "Deals" (business opportunities) among other resources. Specifically, the "Search a Deal" operation allows users to query deals based on various filters and properties, supporting pagination and sorting.

Common scenarios where this node is beneficial include:

• Retrieving deals that match specific criteria for sales reporting or follow-up.
• Automating workflows that require deal data extraction from Rvops.
• Integrating deal information into other systems or dashboards.

For example, you can search for all deals modified after a certain date, filter by deal stage or owner, and retrieve only selected properties such as deal name, amount, and status.

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: "Data De Modificação" (date_modified), "Data De Inclusão" (date_added). Default is "date_modified".
Tipo De Ordenação	Sort order type. Options: "Ascendente" (asc), "Descendente" (desc). Default is "asc".
Filtros	Filters to apply in the search. Each filter includes: - Propriedade Name or ID: property to filter on (loaded dynamically from deal properties). - Filtro/Operador: operator such as equals, not equals, greater than, etc. - Valor a Filtrar: value to compare against.
Propriedade Names or IDs	Additional deal properties to include in the search result. Loaded dynamically from deal properties.
Limit	Maximum number of deals to return in one request. Range 1-100. Default is 100.
Listar Todos	Boolean flag indicating whether to fetch all matching deals at once (true) or limit to the specified number (false).

Output

The output is a JSON array where each item represents a deal matching the search criteria. Each deal object contains:

• id: Unique identifier of the deal.
• properties: An object containing the requested deal properties and their values.
• associations: Related objects linked to the deal (e.g., contacts, companies, products).

No binary data is output by this operation.

Dependencies

• Requires an API key credential (access token) for authenticating requests to the Rvops API.
• The node uses internal helper methods to make HTTP requests to the Rvops API endpoints.
• No additional external dependencies are required beyond the configured API authentication.

Troubleshooting

• Common issues:

  • Invalid or expired access token causing authentication failures.
  • Incorrect filter property names or unsupported operators leading to empty results or errors.
  • Exceeding API rate limits when fetching all results (Listar Todos enabled).
  • Requesting more than the allowed limit per request (max 100).

• Error messages:

  • Authentication errors typically indicate invalid credentials; verify and update the access token.
  • Filter validation errors may occur if property names or operators are incorrect; ensure they match available deal properties.
  • Pagination errors might happen if cursors become invalid; retry the operation or reset pagination.

Links and References

• Rvops API Documentation (hypothetical link)
• n8n Expressions Documentation - for dynamic property specification in filters and properties fields.