Rvops icon

Rvops

Integração Rvops

Actions40

Overview

This node integrates with the Rvops platform to manage and search contacts. Specifically, the "Search a Contact" operation allows users to query contacts based on customizable filters and retrieve selected properties. This is useful in scenarios where you need to find contacts matching specific criteria, such as filtering by name, email, or any other contact property, and then use that data for further automation or analysis.

Practical examples include:

  • Searching for all contacts from a particular city or company.
  • Filtering contacts who have a certain status or tag.
  • Retrieving only specific fields (like email and phone) for matched contacts to reduce data volume.

Properties

Name Meaning
Autenticação Do Cliente Authentication method to access the API. Currently supports "Access Token".
Filtros Filters to apply when searching contacts. Each filter includes:
- Property Name or ID: The contact property to filter by.
- Filter/Operator: Comparison operator such as Equal, Not Equal, Greater Than, Contains, etc.
- Value to filter by.
Propriedade Names or IDs Additional contact properties to include in the search results. You can select from a list or specify IDs via expressions.
Limit Maximum number of contacts to return in the search result. Range: 1 to 100.
Listar Todos Boolean flag indicating whether to list all matching contacts at once, ignoring the limit.
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.

Output

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

  • id: Unique identifier of the contact.
  • properties: An object containing the requested contact properties and their values.
  • associations: Related objects associated with the contact (e.g., companies, deals), if available.

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 functions to make HTTP requests to the Rvops API endpoints.
  • No additional external dependencies beyond the configured API authentication.

Troubleshooting

  • Common issues:

    • Invalid or expired access token will cause authentication failures.
    • Using unsupported or misspelled property names in filters may result in errors or empty results.
    • Requesting more than the allowed limit (over 100) without enabling "Listar Todos" may truncate results.

  • Error messages:

    • Authentication errors typically indicate invalid credentials; verify and update your API token.
    • Filter validation errors occur if the property name or operator is incorrect; check the filter configuration.
    • Rate limiting or server errors from the API should be retried after some delay.

Links and References

Discussion