Rvops

Overview

This node integrates with the Rvops platform to manage and retrieve metadata properties related to various CRM objects. Specifically, for the "Propriedade" (Property) resource with the "List Properties" operation, it fetches a list of properties defined for a selected object type such as contacts, deals, or companies.

Common scenarios where this node is beneficial include:

• Dynamically retrieving available property fields for an object to use in subsequent workflow steps.
• Synchronizing property metadata from Rvops into other systems.
• Building dynamic forms or filters based on current property definitions.

For example, you might use this node to list all contact properties so that you can map them to another system or validate incoming data against existing property definitions.

Properties

Name	Meaning
Autenticação Do Cliente	Method of client authentication; currently supports "Access Token".
Objeto	The object type whose properties you want to list. Options: "Contato" (contact), "Negócio" (deal), "Empresa" (company).

Note: The above properties are relevant to the "List Properties" operation under the "Propriedade" resource.

Output

The output JSON array contains the list of properties for the specified object. Each property item typically includes fields such as:

• id or unique identifier of the property
• label: The display name of the property
• alias or internal name used by the API
• Additional metadata about the property (not explicitly detailed in the source)

This structured output allows workflows to programmatically access property details for further processing.

The node does not output binary data for this operation.

Dependencies

• Requires an API key credential for authenticating requests to the Rvops API.
• Uses HTTP methods (GET) to fetch property data from endpoints like properties/{object}.
• No additional external services beyond the Rvops API are required.

Troubleshooting

• Authentication errors: Ensure the provided API token is valid and has sufficient permissions to read property metadata.
• Empty results: Verify that the selected object type actually has properties defined in the Rvops system.
• API rate limits or connectivity issues: Check network connectivity and API usage quotas.
• Invalid object parameter: Confirm that the "Objeto" parameter is set to one of the supported values ("contact", "deal", "company").

If the node throws errors related to request failures, inspect the error message for HTTP status codes and server messages to diagnose issues.

Links and References

• Rvops API documentation (for properties endpoint): [Not provided in source]
• n8n documentation on creating custom nodes and using credentials: https://docs.n8n.io/
• General REST API best practices for authentication and pagination.