Rvops

Overview

This node integrates with the Rvops platform to manage tasks (among other resources). Specifically, for the "Tarefa" (Task) resource and the "Delete a Task" operation, it allows users to delete a task by specifying its unique ID. This is useful in automation workflows where tasks need to be programmatically removed based on certain conditions or triggers.

Common scenarios include:

• Automatically cleaning up completed or obsolete tasks.
• Removing tasks that were created in error.
• Managing task lifecycle within CRM or project management processes.

Example: A workflow could trigger when a deal is closed, and then delete all related open tasks automatically using this node.

Properties

Name	Meaning
Autenticação Do Cliente	Authentication method to access the API; currently supports "Access Token".
ID Da Tarefa	The unique numeric identifier of the task to delete. This is a required field.

Note: Other properties listed in the full JSON are related to sorting, filtering, or other resources/operations and do not apply to the "Delete a Task" operation.

Output

The output JSON contains the response from the API after attempting to delete the specified task. Typically, this will include confirmation details such as the deleted task's ID or status information.

The structure is an array of JSON objects, each corresponding to an input item processed. If the deletion is successful, the output confirms the action; if there is an error, the output includes an error message and status.

No binary data output is involved in this operation.

Dependencies

• Requires an API key credential for authentication (referred generically as an API access token).
• Depends on the Rvops API endpoint being accessible.
• The node uses internal helper methods to make HTTP requests to the Rvops API and handle pagination or metadata construction.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent task ID will result in an error from the API.
  • Missing or incorrect authentication credentials will cause authorization failures.
  • Network connectivity issues can prevent API calls from succeeding.

• Error messages:

  • Errors returned from the API typically include a message and HTTP status code.
  • The node outputs these errors in the JSON under an error object with fields like message, status, and serverMessage.

• Resolutions:

  • Verify the task ID exists before attempting deletion.
  • Ensure the API access token is valid and has sufficient permissions.
  • Check network connectivity and API endpoint availability.

Links and References

• Rvops API Documentation (hypothetical link for reference)
• n8n documentation on Creating Custom Nodes
• General REST API best practices for error handling and authentication.