Rvops

Overview

This node provides integration with the Rvops platform, enabling automation workflows to interact with various Rvops resources such as contacts, deals, companies, products, users, notes, tasks, associations, properties, and segments. It supports common operations like creating, retrieving, updating, deleting, searching, and listing these resources.

Typical use cases include:

• Managing customer data by creating or updating contacts and companies.
• Handling sales pipelines by managing deals and their stages.
• Organizing product catalogs and inventory.
• Automating task and note management related to CRM activities.
• Segmenting contacts for targeted marketing campaigns.
• Associating different objects within the CRM system.

For example, a user can automate the creation of a new deal when a contact is added, update company information based on external data, or list all products sorted by modification date.

Properties

Name	Meaning
Autenticação Do Cliente	Method of client authentication; currently supports "Access Token".
Campo De Ordenação	Field used to sort results; options vary by resource (e.g., "Data De Modificação", "Data De Inclusão").
Tipo De Ordenação	Sort order type; options are "Ascendente" (ascending) or "Descendente" (descending).
Valor Da Propriedade	For select or multiselect property types, defines the visible name and internal value of each option.
Identificador Unico	Boolean indicating if a property should be unique across objects (applicable for text, textarea, number types).

Sorting fields and order types are available for specific resource lists such as contacts, deals, products, tasks, and segments, with display conditions controlling their visibility.

Output

The node outputs JSON data representing the requested or manipulated resource(s). The structure typically includes:

• id: Unique identifier of the resource.
• properties: An object containing the resource's properties and their values.
• associations: Related linked objects (e.g., associated companies or deals for a contact).

When listing multiple items, the output is an array of such objects. The node also handles pagination internally when listing or searching with options to fetch all results.

No binary data output is indicated in the source code.

Dependencies

• Requires an API key credential for authenticating requests to the Rvops API.
• Uses internal helper functions to make HTTP requests (elozApiRequest) and to format output data.
• No additional external services beyond the Rvops API are required.

Troubleshooting

• Common issues:

  • Authentication failures due to invalid or missing API tokens.
  • Rate limiting or pagination errors when fetching large datasets.
  • Validation errors when creating or updating resources with incorrect or missing properties.

• Error messages:

  • Errors returned from the API include message, status code, and server message, which are passed through in the output under an error field if "Continue On Fail" is enabled.
  • To resolve, verify API credentials, ensure required parameters are provided, and check API limits.

Links and References

• Rvops API Documentation (Assumed URL, replace with actual if known)
• n8n documentation on Creating Custom Nodes
• General REST API usage guidelines for Rvops platform.

---

Note: Internal credential names and service identifiers have been generalized to comply with best practices.