Rvops icon

Rvops

Integração Rvops

Overview

This node integrates with the Rvops platform to manage associations between different objects such as contacts, deals, and companies. Specifically, the "Delete a Association" operation allows users to remove an existing association between two objects by specifying their types and IDs.

Common scenarios where this node is beneficial include:

  • Cleaning up or correcting relationships in CRM data when associations between entities like contacts and companies are no longer valid.
  • Automating the removal of links between deals and contacts after deal closure or cancellation.
  • Managing data integrity by programmatically deleting outdated or incorrect associations.

For example, if a contact was mistakenly linked to a company, this node can be used to delete that association by providing the contact's ID and the company's ID.

Properties

Name Meaning
Autenticação Do Cliente Method of client authentication; currently supports "Access Token".
Objeto De Origem The source object type from which the association will be deleted. Options: "Contato", "Negócio", "Empresa".
ID Do Objeto Da Origem The numeric ID of the source object to delete the association from. Must be ≥ 1.
Objeto De Destino The target object type to which the association will be deleted. Options: "Contato", "Negócio", "Empresa".
ID Do Objeto De Destino The numeric ID of the target object to delete the association from. Must be ≥ 1.

Note: Other properties listed in the full input are not relevant for the "Delete a Association" operation.

Output

The output JSON contains the response from the API call to delete the association. Typically, this will be an object confirming the deletion or containing status information. The exact structure depends on the API but generally includes success confirmation or error details.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential (referred generically as an access token) for authenticating requests to the Rvops API.
  • The node uses HTTP methods (DELETE) to interact with the Rvops API endpoints.
  • No additional external services or environment variables are explicitly required beyond the API authentication.

Troubleshooting

  • Common Issues:

    • Providing invalid or non-existent object IDs will likely result in errors from the API indicating the resource was not found.
    • Incorrect object type combinations (e.g., trying to delete an association between unsupported object types) may cause failures.
    • Missing or invalid authentication token will 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 about authorization, verify that the access token is correct and has sufficient permissions.
    • For "not found" errors, confirm that the provided object IDs exist and are correctly typed.
  • Resolution:

    • Double-check all input parameters for correctness.
    • Ensure the API token is valid and active.
    • Review API documentation for supported object types and association rules.

Links and References


This summary focuses exclusively on the "Delete a Association" operation within the "Associação" resource as requested.

Discussion