Rvops

Overview

This node integrates with the Rvops platform to manage various CRM-related resources, including contacts. Specifically, for the "Contato" (Contact) resource and the "Delete a Contact" operation, it allows users to delete a contact by specifying its unique ID. This is useful in scenarios where you need to remove outdated or incorrect contact records from your CRM system automatically as part of a workflow.

Practical examples include:

• Automatically deleting contacts who have unsubscribed from communications.
• Cleaning up test or duplicate contacts after data import.
• Removing contacts based on certain triggers or conditions in an automated pipeline.

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 be deleted. This is required for the delete operation.

Note: Other properties listed in the provided JSON are related to sorting, filtering, and other operations but are not relevant for the "Delete a Contact" operation.

Output

The output of the delete operation is the response returned by the API after attempting to delete the contact. It is wrapped into the node's standard execution metadata format. Typically, this will contain confirmation of deletion or details about the deleted contact.

The json output field contains the API response object, which may include fields such as:

• id: The ID of the deleted contact.
• Other metadata confirming the deletion status.

No binary data output is involved in this operation.

Dependencies

• Requires an API key credential for authenticating requests to the Rvops platform.
• The node uses internal helper methods to make HTTP requests to the Rvops API endpoints.
• No additional external services beyond the Rvops API are required.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent contact ID will likely result in an error from the API.
  • Missing or incorrect API authentication token will cause authentication failures.
  • Network connectivity issues can prevent successful API calls.

• Error messages:

  • Errors returned from the API typically include a message and HTTP status code.
  • If the node throws an error indicating failure to delete, verify that the contact ID exists and that the API credentials are valid.
  • To handle errors gracefully, enable the node's "Continue On Fail" option to capture error details in the output.

Links and References

• Rvops API Documentation (Assumed URL, replace with actual if known)
• n8n documentation on Creating Custom Nodes
• General REST API best practices for delete operations

---

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