Rvops icon

Rvops

Integração Rvops

Actions40

Overview

This node integrates with the Rvops platform to manage various CRM-related resources, including deals (Negócio). Specifically, for the "Delete a Deal" operation under the "Negócio" resource, it allows users to delete a deal by specifying its unique identifier. This is useful in scenarios where deals are no longer relevant or were created erroneously and need to be removed from the system.

Practical examples:

  • Automatically deleting deals that have been marked as lost or cancelled in an external system.
  • Cleaning up test or duplicate deals during data synchronization workflows.
  • Removing deals after certain business conditions are met, such as contract expiration.

Properties

Name Meaning
Autenticação Do Cliente Authentication method to access the API; currently supports "Access Token".
ID Do Negócio The unique numeric identifier of the deal to be deleted. This is a required field.

Note: Other properties listed in the full node definition relate to other operations or resources and are not applicable to the "Delete a Deal" operation.

Output

The output JSON contains the response from the API after attempting to delete the specified deal. Typically, this will include confirmation details or status information about the deletion operation. The structure includes:

  • id: The identifier of the deal affected.
  • Other metadata or confirmation fields as returned by the API.

If an error occurs, the output will contain an error object with:

  • message: A description of the error.
  • status: HTTP status code from the server.
  • serverMessage: Detailed message from the server.

No binary data output is involved in this operation.

Dependencies

  • Requires an active API authentication token credential to authorize requests.
  • Depends on the Rvops API endpoint for deals management.
  • The node uses internal helper functions to make HTTP DELETE requests to the endpoint deals/{id}.

Troubleshooting

  • Common issues:

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

  • Error messages:

    • "404 Not Found": The deal ID does not exist. Verify the ID before retrying.
    • "401 Unauthorized": Authentication failed. Check the API token validity.
    • "400 Bad Request": The request parameters are incorrect or incomplete.

  • Resolution tips:

    • Ensure the deal ID is correct and exists in the system.
    • Refresh or reconfigure the API authentication token if unauthorized errors occur.
    • Review the node's input parameters for completeness and correctness.

Links and References

Discussion