Rvops

Overview

This node integrates with the Rvops platform to manage tasks (Tarefa) among other resources. Specifically, the "List Tasks" operation retrieves a list of tasks from the Rvops system. It supports pagination and sorting, and can optionally watch for new tasks since the last execution using a cursor mechanism.

Common scenarios where this node is beneficial include:

• Automating task management workflows by fetching current tasks.
• Monitoring newly created or updated tasks incrementally.
• Integrating task data into other systems or processes for reporting or triggering actions.

For example, you could use this node to regularly fetch all tasks assigned to a team, sorted by their due date, and then send reminders or update statuses in another system.

Properties

Name	Meaning
Autenticação Do Cliente	Authentication method; currently only "Access Token" is supported.
Limit	Maximum number of tasks to return per request (1 to 100).
Listar Todos	Boolean flag to list all tasks at once, ignoring pagination limits.
Monitorar Novos Valores	Boolean flag to enable watching for new tasks since the last run using a cursor. Defaults to true.
Campo De Ordenação	Field to sort the results by; options are "Data De Modificação" (updatedAt) or "Data De Inclusão" (createdAt).
Tipo De Ordenação	Sort order type; options are "Ascendente" (ascending) or "Descendente" (descending).

Note: Some properties like sorting fields and order have display conditions based on whether watching is enabled or not.

Output

The output is a JSON array where each item represents a task object with the following structure:

• id: Unique identifier of the task.
• properties: An object containing the task's properties such as name, owner, due date, priority, description, task type, source, etc.

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential for authentication (referred generically as an API access token).
• Depends on the Rvops API endpoint for tasks.
• Uses internal helper methods to make HTTP requests and handle pagination cursors.
• The node stores static workflow data to keep track of the last cursor when watching for new tasks.

Troubleshooting

• Common issues:

  • Invalid or expired API token will cause authentication failures.
  • Exceeding the maximum limit (over 100) will likely result in errors.
  • Incorrect sorting field or order values may cause unexpected results or API errors.
  • If "Monitorar Novos Valores" is enabled but no cursor is stored yet, it will start listing from the beginning.

• Error messages:

  • Errors returned from the API are captured and included in the output if "Continue On Fail" is enabled.
  • Typical error messages include authentication errors, invalid parameters, or rate limiting.

• Resolutions:

  • Ensure the API token is valid and has necessary permissions.
  • Use the "Limit" property within allowed range.
  • Verify sorting options match the API's expected values.
  • Clear or reset the node's static data if cursor-related issues occur.

Links and References

• Rvops API Documentation (generic placeholder link)
• n8n documentation on Creating Custom Nodes
• Pagination and cursor handling concepts in REST APIs

---

This summary focuses exclusively on the "Tarefa" resource and its "List Tasks" operation as requested.