Rvops icon

Rvops

Integração Rvops

Actions40

Overview

This node integrates with the Rvops platform to manage various CRM-related resources, including tasks. Specifically, for the Tarefa (Task) resource and the Get a Task operation, the node retrieves detailed information about a single task by its unique identifier.

Typical use cases include:

  • Fetching task details to display or process in workflows.
  • Automating follow-ups or reminders based on task properties.
  • Integrating task data into other systems or reports.

For example, you might use this node to get the status, due date, owner, and description of a specific task to trigger notifications or update related records elsewhere.

Properties

Name Meaning
Autenticação Do Cliente Method of client authentication; currently supports "Access Token" only.
ID Da Tarefa The unique numeric identifier of the task to retrieve. This is required for the operation.

Note: Other properties listed in the full JSON are general or related to other resources/operations and do not apply specifically to the "Get a Task" operation.

Output

The output JSON object for the "Get a Task" operation includes:

  • id: The unique identifier of the task.
  • properties: An object containing all the task's properties such as name, owner, due date, priority, description, type, source, and any custom fields defined in the system.

No binary data output is involved in this operation.

Example output structure (simplified):

{
  "id": 123,
  "properties": {
    "name": "Follow up call",
    "owner": "user_456",
    "due_date": "2024-07-01T12:00:00Z",
    "priority": "high",
    "description": "Call the client to discuss contract renewal",
    "task_type": "call",
    "source": "manual"
  }
}

Dependencies

  • Requires an API key credential for authentication (referred generically as an API access token).
  • Depends on the Rvops API endpoint accessible via HTTP requests.
  • No additional external services are required beyond the configured API credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing task ID: The node requires a valid numeric task ID; ensure it is provided and correct.
    • Authentication errors: Verify that the API access token is valid and has sufficient permissions.
    • Network or API downtime: Check connectivity and Rvops service status if requests fail.

  • Error messages:

    • Errors returned from the API will be included in the output if "Continue On Fail" is enabled.
    • Typical error messages may include "Not Found" if the task ID does not exist, or "Unauthorized" if the token is invalid.

  • Resolution tips:

    • Double-check the task ID input.
    • Refresh or reconfigure the API credentials.
    • Review API rate limits or permissions.

Links and References

Discussion