Rvops

Overview

This node integrates with the Rvops platform to manage tasks (Tarefa resource), specifically allowing you to update an existing task. It is useful in automation workflows where you need to modify task details such as name, owner, description, due date, priority, type, or source based on dynamic inputs or external triggers.

Typical use cases include:

• Updating task information when a related deal or contact changes.
• Adjusting task priorities or deadlines automatically based on workflow conditions.
• Changing task ownership or type programmatically to reflect new assignments or communication channels.

For example, you could automate updating a task’s due date and priority when a customer escalates an issue, ensuring timely follow-up.

Properties

Name	Meaning
ID Da Tarefa	The unique numeric identifier of the task to update (required).
Nome Da Tarefa	The new name/title for the task.
Proprietário Da Tarefa Name or ID	The owner of the task, selectable from a list or specified by ID/expression.
Descricão Da Tarefa	A textual description or notes about the task.
Data E Hora Do Vencimento Da Tarefa	The due date and time for the task completion.
Prioridade	Priority level of the task; options are Baixa (Low), Média (Medium), Alta (High).
Tipo	Type of task; options include To Do, Ligação (Call), E-Mail, WhatsApp. (required)
Origem	Source or origin information of the task.

Output

The node outputs JSON data representing the updated task object. The structure includes:

• id: The unique identifier of the updated task.
• properties: An object containing all updated properties of the task, reflecting the changes made.

No binary data output is involved.

Example output JSON snippet:

{
  "id": 123,
  "properties": {
    "name": "Follow up call",
    "owner": "user_456",
    "description": "Updated task description",
    "due_date": "2024-07-01T15:00:00Z",
    "priority": "2",
    "task_type": "call",
    "source": "CRM Automation"
  }
}

Dependencies

• Requires an API key credential for authentication with the Rvops platform.
• Uses HTTP methods (PATCH) to interact with the Rvops API endpoint for tasks.
• No additional external services beyond the Rvops API are required.
• Ensure the node has proper network access and valid credentials configured in n8n.

Troubleshooting

• Common issues:

  • Invalid or missing task ID will cause the update to fail.
  • Providing invalid values for enumerated fields like priority or type may result in API errors.
  • Network or authentication failures can prevent successful API calls.

• Error messages:

  • Errors returned from the API typically include a message and status code.
  • If the node is set to continue on failure, error details are included in the output JSON under an error field.

• Resolutions:

  • Verify that the task ID exists and is correct.
  • Use only supported values for priority and type fields.
  • Confirm that the API key credential is valid and has necessary permissions.
  • Check network connectivity and API endpoint availability.

Links and References

• Rvops API Documentation (hypothetical link)
• n8n Expressions Documentation
• n8n Credential Management

---

This summary focuses exclusively on the "Update a Task" operation within the "Tarefa" resource, based on the provided source code and input property definitions.