Rvops

Overview

This node integrates with the Rvops platform to manage contacts and other related resources. Specifically, for the Contato (Contact) resource with the List Contacts operation, it retrieves a list of contacts from the Rvops system based on various filtering, sorting, and pagination options.

Common scenarios where this node is beneficial include:

• Synchronizing contact data from Rvops into another system or workflow.
• Monitoring new or updated contacts by incrementally fetching changes since the last run.
• Filtering contacts by campaign or segment membership.
• Retrieving specific properties of contacts for reporting or further processing.

Practical example:

• A marketing automation workflow that fetches all contacts belonging to a particular segment or campaign, processes them, and sends personalized emails.
• A CRM integration that periodically lists all contacts modified since the last execution to update local records.

Properties

Name	Meaning
Autenticação Do Cliente	Authentication method to use; currently supports "Access Token".
Limite	Maximum number of contacts to return in one request (minimum 1).
ID Do Fluxo De Automação	Filter contacts that meet the criteria of a specific automation flow (campaign ID).
ID Do Segmento	Filter contacts that belong to a specific segment ID.
Propriedade Names or IDs	Additional contact properties to include in the response. You can select from a list or specify property IDs via expressions.
Listar Todos	Boolean flag indicating whether to list all matching contacts at once (ignores limit and paginates internally).
Monitorar Novos Valores	Boolean flag indicating whether to fetch contacts starting from the last cursor position stored in the workflow static data, enabling incremental listing of new or updated contacts.
Campo De Ordenação	Field to sort the results by; options are "Data De Modificação" (date_modified) or "Data De Inclusão" (date_added). Defaults to date_modified when not watching for new values.
Tipo De Ordenação	Sort order type; either Ascendente (ascending) or Descendente (descending). Defaults to ascending when not watching for new values.

Output

The output is an array of JSON objects representing contacts. Each contact object includes:

• id: The unique identifier of the contact.
• properties: An object containing the requested contact properties and their values.
• associations: Related entities associated with the contact (e.g., companies, deals).

The output is structured to allow easy access to contact details and their relationships within the Rvops system.

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential for authentication with the Rvops API (referred generically as an API token).
• Uses HTTP requests to the Rvops REST API endpoints for contacts.
• The node relies on internal helper methods for making authenticated API calls and handling pagination cursors.
• Workflow static data storage is used to keep track of cursors for incremental fetching when "Monitorar Novos Valores" is enabled.

Troubleshooting

• Issue: No contacts returned despite existing data

  • Check if filters such as Segment ID or Campaign ID are set correctly.
  • Verify that the API token has sufficient permissions to read contacts.
  • If using incremental fetching ("Monitorar Novos Valores"), ensure the cursor is valid or try disabling it to fetch all data.

• Error: API request failures or timeouts

  • Confirm network connectivity to the Rvops API.
  • Validate that the API token is correct and not expired.
  • Review rate limits imposed by the API and adjust the "Limite" or "Listar Todos" settings accordingly.

• Error messages including status codes and server messages

  • These are returned in the output under an error field if "Continue On Fail" is enabled.
  • Use the error message and status code to diagnose issues such as unauthorized access (401), forbidden (403), or bad requests (400).

Links and References

• Rvops API Documentation (hypothetical link, replace with actual if available)
• n8n Expressions Documentation — for specifying dynamic property names or IDs
• General n8n documentation on API Credentials and Node Development

---

This summary focuses exclusively on the Contact resource's List Contacts operation as requested, based on static analysis of the provided source code and input property definitions.