Rvops

Overview

This node integrates with the Rvops platform to manage contacts and other related resources. Specifically, for the "Contato" (Contact) resource and the "Update a Contact" operation, it allows users to update existing contact records by specifying the contact's unique ID and the properties to be updated.

Common scenarios where this node is beneficial include:

• Synchronizing contact information from external systems into Rvops.
• Automating updates to contact details based on workflow triggers.
• Maintaining up-to-date customer data in marketing or sales automation processes.

For example, you might use this node to update a contact's email address or phone number after receiving new information from a form submission or CRM system.

Properties

Name	Meaning
Autenticação Do Cliente	Method of client authentication; currently supports "Access Token".
ID Do Contato	The unique identifier of the contact to update. This is required to specify which contact to modify.
Propriedades	A collection of properties to update on the contact. Each property includes:
	- Nome Da Propriedade Name or ID: The name or ID of the contact property to update.
	- Novo valor: The new value to assign to the specified property.

Note: Other properties listed in the full JSON are related to sorting and listing operations or other resources and do not apply directly to the "Update a Contact" operation.

Output

The output of the node after updating a contact is a JSON object containing:

• id: The unique identifier of the updated contact.
• properties: An object representing the updated properties of the contact.

The output is structured as an array of such objects, each corresponding to an input item processed by the node. No binary data output is produced by this operation.

Example output JSON structure:

[
  {
    "id": "contact-id-123",
    "properties": {
      "email": "new.email@example.com",
      "phone": "+1234567890"
    }
  }
]

Dependencies

• Requires an API key credential for authenticating requests to the Rvops platform.
• The node uses internal helper methods to make HTTP PATCH requests to the Rvops API endpoint for contacts.
• No additional external dependencies beyond the configured API credentials and network access to the Rvops API.

Troubleshooting

• Invalid Contact ID: If the provided contact ID does not exist, the API will likely return an error indicating the contact was not found. Verify the ID is correct.
• Authentication Errors: Ensure that the API token used is valid and has sufficient permissions to update contacts.
• Property Validation: If attempting to update properties that do not exist or are invalid, the API may reject the request. Confirm property names/IDs are correct and supported.
• Network Issues: Connectivity problems to the Rvops API endpoint can cause failures. Check network settings and API availability.
• Continue On Fail: The node supports continuing execution on failure for individual items, returning error details in the output JSON under an error field.

Links and References

• Rvops API Documentation (hypothetical link, replace with actual if available)
• n8n Expressions Guide: Using Expressions (for dynamic property IDs)

---

This summary focuses exclusively on the "Contato" resource and the "Update a Contact" operation as requested.