Voalle icon

Voalle

Interact with Voalle API

Actions64

Service Desk → Consultar Agendamentos Do FSM

AI-generated

Overview

This node interacts with the Voalle API specifically for the Service Desk resource to consult FSM (Field Service Management) schedules. It allows users to query schedules within a specified date range and filter by technician CPF, protocol, routing status, and region code. This is useful for managing and tracking field service appointments and technician assignments.

Use Case Examples

  1. A service manager wants to retrieve all FSM schedules for a specific technician within a date range to review workload and appointments.
  2. A support team needs to filter FSM schedules by routing status to identify pending or completed field service tasks.

Properties

Name Meaning
Data Inicial The start date for querying FSM schedules, required to define the initial date range for the search.
Data Final The end date for querying FSM schedules, optional to define the final date range for the search.
CPF Do Tecnico The CPF (tax ID) of the technician to filter schedules assigned to a specific technician.
Protocolo The protocol number to filter schedules related to a specific service request or ticket.
Status Da Roteirizacao The routing status to filter schedules based on their routing state.
Codigo Da Regiao The region code to filter schedules by geographic or operational region.

Output

JSON

  • json - The JSON response from the Voalle API containing the list of FSM schedules matching the query parameters.

Dependencies

  • Voalle API authentication credentials

Troubleshooting

  • Ensure the required 'Data Inicial' parameter is provided; missing this will cause the node to fail.
  • Verify that the Voalle API credentials are correctly configured and have the necessary permissions to access Service Desk FSM schedules.
  • Check the date formats for 'Data Inicial' and 'Data Final' to ensure they comply with the API requirements.
  • If the API returns an error about invalid filters, verify that optional parameters like CPF, protocol, routing status, and region code are correctly formatted and valid.

Discussion