Rvops

Overview

The node provides integration with the Rvops platform, allowing users to interact with various resources such as contacts, deals, companies, products, tasks, notes, associations, properties, segments, and users. Specifically, for the Segmento resource with the List Segments operation, the node fetches a list of segments from the Rvops system.

This operation is useful when you want to retrieve segment data for further processing, reporting, or automation workflows. For example, you might use it to:

• Synchronize segment lists with another system.
• Trigger actions based on new or updated segments.
• Analyze segment metadata for marketing or sales purposes.

The node supports pagination and cursor-based incremental fetching, enabling efficient handling of large datasets.

Properties

Name	Meaning
Autenticação Do Cliente	Authentication method; currently supports "Access Token".
Limit	Maximum number of segments to return (1 to 100).
Listar Todos	Whether to list all segments at once, ignoring the limit.
Monitorar Novos Valores	If enabled, the node will fetch segments incrementally using a stored cursor to get only new/updated ones.
Campo De Ordenação	Field to sort the results by; options: "Data De Modificação" (date_modified), "Data De Inclusão" (date_added).
Tipo De Ordenação	Sort order type; options: "Ascendente" (asc), "Descendente" (desc).

Output

The output is an array of JSON objects representing segments retrieved from the Rvops API. Each segment object typically contains fields such as:

• id: Unique identifier of the segment.
• Other segment-specific properties returned by the API.

The node uses n8n's helper methods to attach execution metadata to each item, preserving context about the input item index.

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential for authentication (referred generically as "an API key credential").
• The node makes HTTP requests to the Rvops API endpoints.
• No additional external dependencies are required beyond standard n8n environment setup.

Troubleshooting

• Common issues:

  • Invalid or expired API token: The node will fail to authenticate. Ensure the API key credential is valid and has necessary permissions.
  • Exceeding rate limits: If many requests are made in a short time, the API may throttle calls.
  • Cursor management: When using incremental fetching ("Monitorar Novos Valores"), if the stored cursor becomes invalid or corrupted, the node may not fetch expected data.

• Error messages:

  • Errors from the API are captured and returned in the output as error objects with message and status.
  • Network or connectivity errors will cause the node to throw exceptions unless "Continue On Fail" is enabled.

• Resolutions:

  • Verify API credentials and permissions.
  • Adjust request frequency or enable pagination properly.
  • Reset or clear workflow static data if cursor issues occur.

Links and References

• Rvops API Documentation (Assumed URL, replace with actual if known)
• n8n documentation on HTTP Request Node for understanding API interactions.
• n8n documentation on Working with Pagination and Cursors for best practices on incremental data fetching.