Actions120
- Authentication Actions
- Bloqueios Actions
- Get Motivos
- Get Bloqueio Faturamento
- Get Bloqueio Conta
- Get Bloqueio Carteira
- Get Bloqueio Compra Pedido
- Get Bloqueio Cotacao Compra
- Get Bloqueio Data Minima Vencimento
- Get Bloqueio Estoque Negativo
- Get Bloqueio Financiamento Pedido
- Get Bloqueio Frete Pago
- Get Bloqueio Limite Credito
- Get Bloqueio Limite Individual
- Get Bloqueio Manutencao Preventiva
- Get Bloqueio Margem
- Get Bloqueio Mes Reajuste
- Get Bloqueio Parcela Minima
- Get Bloqueio Saldo Atrasado
- Desaprovar Bloqueio
- Liberar Bloqueio
- Liberar Bloqueio Limite Credito
- Liberar Bloqueio Limite Individual
- Classificacao Actions
- Cliente Actions
- Instituição Financeira Actions
- Linha de Crédito Actions
- Máquina Actions
- Mecânico Actions
- Motorista Actions
- Negócio Actions
- Nota Fiscal Actions
- Oficina Actions
- Orçamento Actions
- Orçamento Balcão Actions
- Ordem de Serviço Actions
- Criar Ordem de Serviço Completa
- Consultar por ID
- Consultar por Código Externo
- Listar Agendamentos
- Listar Agendamentos por ID
- Listar Status do Lock
- Listar Ordens de Serviço
- Incluir Ordem de Serviço
- Listar Ordens de Serviço Geral
- Incluir Apontamento
- Incluir Despesa
- Incluir Peça
- Incluir Serviço
- Editar Peça
- Editar Serviço
- Editar Veículo
- Incluir Observação
- Ordem Serviço Tipo Actions
- Pedido Actions
- Política de Prazo Actions
- Política de Preço Actions
- Produto Actions
- Prospect Actions
- Saída Actions
- Serviço Actions
- Status Financiamento Actions
- Título Actions
- Veículo Cliente Actions
- Veículo Próprio Actions
- Vendas Actions
- Vendedor Actions
Saída → Include Saida
AI-generatedOverview
The "Include Saida" operation of the "Saída" resource in this node allows users to include a new output record related to service orders or vehicle attendances within the Nuvem Solution system. This operation is useful for tracking and registering details about vehicle dispatches, including mileage, dates, times, drivers, and reasons for the output.
Typical use cases include:
- Logging the departure and return details of vehicles used for service orders.
- Recording mileage data associated with vehicle usage.
- Tracking driver assignments and reasons for vehicle dispatches.
- Integrating vehicle output data into broader service order management workflows.
For example, a fleet manager could automate the recording of vehicle dispatches and returns, ensuring accurate mileage tracking and driver accountability without manual entry.
Properties
| Name | Meaning |
|---|---|
| Filial ID | Numeric identifier of the branch or subsidiary where the output is registered. |
| Veículo Atendimento ID | Numeric identifier of the vehicle assigned for the attendance or service. |
| Motorista ID | Numeric identifier of the driver responsible for the vehicle during the output period. |
| Saída de OS | Indicates if the output is related to a service order; options: "Indefinido", "Não", "Sim". |
| Saída KM | Numeric value representing the vehicle's odometer reading at the time of departure. |
| Data de Saída | Date and time when the vehicle departed (ISO 8601 format). |
| Hora de Saída | Time of departure in "HH:MM" format (optional). |
| Retorno KM | Numeric value representing the vehicle's odometer reading upon return. |
| Data de Retorno | Date and time when the vehicle returned (ISO 8601 format). |
| Hora de Retorno | Time of return in "HH:MM" format (optional). |
| KM Custo | Numeric value indicating the cost-related mileage for the trip. |
| Motivo | Text field for specifying the reason for the output, up to 1200 characters (optional). |
Output
The node outputs a JSON object containing the response from the Nuvem Solution API after including the new output record. The structure typically includes confirmation details such as IDs, timestamps, and status messages confirming the successful inclusion of the output.
No binary data is produced by this operation.
Dependencies
- Requires an active connection to the Nuvem Solution API.
- Requires credentials including a software key, secret, user ID, and user key for authentication.
- The node uses bearer token authentication obtained via these credentials.
- Proper configuration of the API base URL and valid credentials are necessary for successful requests.
Troubleshooting
- Authentication Errors: If authentication fails, verify that the software key, secret, user ID, and user key are correctly configured and have not expired.
- Invalid or Missing Required Fields: Ensure all required properties (e.g., Filial ID, Veículo Atendimento ID, Motorista ID, Saída KM, etc.) are provided and valid.
- Date and Time Format Issues: Dates should be in ISO 8601 format, and times should follow the "HH:MM" format. Incorrect formats may cause API errors.
- API Endpoint Errors: Network issues or incorrect base URLs can cause request failures. Confirm the API endpoint is reachable and correct.
- Permission Denied: The authenticated user must have permissions to include outputs; otherwise, the API will reject the request.
Links and References
- Nuvem Solution API Documentation (general reference, actual documentation URL may vary)
- n8n Documentation - Creating Custom Nodes
- ISO 8601 Date and Time Format
This summary is based on static analysis of the node's source code and provided property definitions, focusing specifically on the "Include Saida" operation of the "Saída" resource.