Rvops icon

Rvops

Integração Rvops

Actions40

Overview

This node integrates with the Rvops platform to manage various CRM-related resources, including properties of objects such as contacts, deals, and companies. Specifically, for the "Propriedade" (Property) resource with the "Create a Propertie" operation, it allows users to create custom properties on specified objects within the CRM system.

Use cases include:

  • Adding new custom fields to contacts, deals, or companies to capture additional data not covered by default fields.
  • Defining property types such as text, number, date, select options, etc., to tailor data collection.
  • Enforcing uniqueness or mandatory status on certain properties to maintain data integrity.

Practical example:

  • Creating a new "Customer Tier" select property on contacts with options like "Gold", "Silver", and "Bronze".
  • Adding a unique identifier property to deals to track external system IDs.

Properties

Name Meaning
Autenticação Do Cliente Authentication method to use; currently supports "Access Token".
Objeto Da Propriedade The object type where the property will be created. Options: "Contato" (contact), "Negócio" (deal), "Empresa" (company).
Nome Da Nova Propriedade The name of the new property to create.
Tipo Da Propriedade The data type of the property. Options include: "Data" (date), "Data E Hora" (datetime), "Seleção" (select), "Seleção Múltipla" (multiselect), "Texto" (text), "Área De Texto" (textarea), "Hora" (time), "Número" (number), "Usuário" (user).
Valor Da Propriedade When the property type is "select" or "multiselect", this defines the selectable options. Each option has a visible name ("Nome") and an internal value ("Valor Interno").
Obrigatório Boolean flag indicating if the property is required (mandatory).
Identificador Unico Boolean flag indicating if the property should be a unique identifier (no duplicate values allowed). Only applicable for text, textarea, and number types.

Output

The node outputs JSON data representing the newly created property. The output includes at least the following structure:

{
  "id": "<property_id>",
  "properties": {
    "object": "<object_type>",
    "group": "core",
    "name": "<property_name>",
    "type": "<property_type>",
    "isRequired": <boolean>,
    "isUniqueIdentifier": <boolean>,
    "properties": {
      "list": [
        {
          "label": "<option_label>",
          "value": "<option_value>"
        }
      ]
    }
  }
}
  • id: Identifier of the created property.
  • properties: Details about the property configuration.
  • If the property type is select or multiselect, the properties.list contains the available options.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authentication with the Rvops platform.
  • Uses HTTP requests to the Rvops API endpoints to create properties.
  • No additional external dependencies beyond the configured API access.

Troubleshooting

  • Common issues:

    • Missing or invalid API authentication token will cause authorization errors.
    • Attempting to create a property with a name that already exists may result in an error from the API.
    • For select/multiselect types, failing to provide at least one option will likely cause validation errors.
    • Setting uniqueness on unsupported property types (other than text, textarea, number) may be ignored or rejected.

  • Error messages:

    • Authorization errors: Check that the API key is correctly configured and valid.
    • Validation errors: Ensure all required fields are filled, especially property name and type.
    • API response errors may include messages about duplicate property names or invalid option formats.

Links and References

Discussion