Rvops

Overview

This node integrates with the Rvops platform to manage tasks (Tarefa). Specifically, the "Create a Task" operation allows users to create new tasks within the system. This is useful for automating task creation workflows such as scheduling follow-ups, assigning responsibilities, or tracking activities related to deals and contacts.

Practical examples include:

• Automatically creating a task to follow up on a sales lead by associating it with relevant deals and contacts.
• Scheduling reminders or calls with specific owners and priorities.
• Logging tasks originating from automated processes or external triggers, with detailed descriptions and due dates.

Properties

Name	Meaning
Autenticação Do Cliente	Method of client authentication; currently supports "Access Token".
Nome Da Tarefa	The name/title of the task to be created.
Proprietário Da Tarefa Name or ID	The owner of the task; selectable from a list or specified by ID.
Descricão Da Tarefa	Optional description providing details about the task.
Data E Hora Do Vencimento Da Tarefa	Due date and time when the task should be completed.
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.
Origem	Source/origin of the task; default is "N8N".
Associações Com Negócios	Associations with deals/businesses; multiple deal IDs can be linked to the task.
Associações Com Contatos	Associations with contacts; multiple contact IDs can be linked to the task.

Output

The output JSON contains the newly created task object with at least the following structure:

{
  "id": "string",
  "properties": {
    "name": "string",
    "owner": "string or number",
    "due_date": "ISO8601 datetime string",
    "priority": "string (numeric)",
    "task_type": "string",
    "description": "string (optional)",
    "source": "string (optional)"
  }
}

• id: Unique identifier of the created task.
• properties: Contains all task details as submitted.
• If associations were provided, they are included in the creation request but not explicitly shown in the output snippet; typically, the API response includes them.

No binary data output is involved in this operation.

Dependencies

• Requires an API key credential for authenticating requests to the Rvops platform.
• The node uses HTTP methods (POST) to communicate with the Rvops API endpoints.
• No additional environment variables are explicitly required beyond the API authentication token.

Troubleshooting

• Missing Required Fields: Errors may occur if mandatory fields like task name, owner, due date, priority, or type are missing. Ensure these are provided.
• Invalid Owner ID: Selecting an invalid or non-existent owner ID will cause API errors. Use the provided load options to select valid owners.
• Association IDs: Providing invalid deal or contact IDs in associations may result in failures or incomplete associations.
• API Authentication Failures: Ensure the API token is valid and has sufficient permissions.
• Date Format Issues: The due date must be in a valid ISO8601 format; incorrect formats may cause errors.
• Network or API Errors: Handle transient network issues or API downtime gracefully, possibly using the node's "Continue On Fail" option.

Links and References

• n8n Expressions Documentation
• Rvops API documentation (not publicly linked here; refer to your Rvops API docs for endpoint details)
• n8n HTTP Request Node documentation for understanding API interactions

---

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